Move .env and .env.example into root of repo#189
Merged
Move .env and .env.example into root of repo#189
Conversation
validbeck
approved these changes
May 9, 2024
Collaborator
validbeck
left a comment
There was a problem hiding this comment.
Moves the .env.example file up a level into the root of the repo so it's not in Quarto's way
success!
Modifies the release notes script to look for a .env file in the root of the repo
nöice, it works
Updates .gitignore to fix the path for the .quarto folder (which does need to be inside of site/)
not sure what this change does but it's there!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Internal Notes for Reviewers
Next try! This PR:
.env.examplefile up a level into the root of the repo so it's not in Quarto's way.envfile in the root of the repo.gitignoreto fix the path for the.quartofolder (which does need to be inside ofsite/)Tested the release notes script after the update to make sure everything works:
External Release Notes