added .env to .gitignore #76
Closed
Conversation
This file contains 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
fixes AOSSIE-Org#71 what i have done: Added .env in .gitignore file this PR will make the env file get removed from repo online and in future it will not get pushed back to repo if any changes detected by git additonal note: To fully address the issue, the .env file should be removed from the Git history using tools like BFG Repo-Cleaner or git filter-branch. Additionally, any sensitive keys or credentials should be rotated to ensure they are secure.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #71
what i have done:
Added .env in .gitignore file
this PR will make the env file get removed from repo online and in future it will not get pushed back to repo if any changes detected by git
additonal note:
To fully address the issue, the .env file should be removed from the Git history using tools like BFG Repo-Cleaner or git filter-branch. Additionally, any sensitive keys or credentials should be rotated to ensure they are secure.
AND
repo owner should replace the old variable values used in current env to new values