Updated configuration of env vars to avoid gitleaks failure#14
Merged
itsskofficial merged 2 commits intomasterfrom Feb 23, 2025
Merged
Updated configuration of env vars to avoid gitleaks failure#14itsskofficial merged 2 commits intomasterfrom
itsskofficial merged 2 commits intomasterfrom
Conversation
chore: updated readme, pr workflow and env template files
itsskofficial
added
bug
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
🚀 Summary
Keeping values in the .env.template is not feasible as it leads to gitleaks status check failure. So, I created a new mechanism in which the template file would be empty. The contributor has to refer the README and fill his/hers own file. Along with that, If the contributor wants any pre-setup sensitive env variables, he/she can comment in this discussion
🔍 Changes Made