Add {prod, dev, whatever_enviroment}.secret.exs in Elixir/Phoenix - #2611
Merged
Conversation
GusGA
changed the title
Member
|
@GusGA thanks! |
Contributor
Author
|
To you, for letting me collaborate. |
rhcarvalho
added a commit
to rhcarvalho/gitignore
that referenced
this pull request
Aug 2, 2026
Update Elixir.gitignore to match the upstream template for new Elixir projects. https://github.com/elixir-lang/elixir/blob/a9021b1c8d932fd5cf2339e4536c5c9ef024003f/lib/mix/lib/mix/tasks/new.ex#L307-L331 Remove `.fetch` which was also removed upstream (elixir-lang/elixir#13871). Preserve additional patterns added in github#2132, github#2611, and github#2872, adding comments to match the style of the rest of the file.
1 task
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.
Reasons for making this change:
The config/prod.secret.exs file by default contains sensitive data and you should not commit it into version control. But can exist other configurations in the development environment that should not be shared like every developer database configuration because could be annoying to the rest of the team
Links to documentation supporting these rule changes:
Phoenix documentation site Link