Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ShellScript] Apply to .env #3496

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ShellScript/Bash.sublime-syntax
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ file_extensions:
- bashrc # e.g.: /etc/bash.bashrc
- ash
- zsh
- env

hidden_file_extensions:
- .bash_aliases
Expand All @@ -24,6 +25,7 @@ hidden_file_extensions:
- .bash_profile
- .bash_variables
- .bashrc
- .env
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've also seen .env.local for environment variables which are only sourced for the local development environment. I'm not sure how common it is and whether it would be worth adding this as well?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No real opinion here, but if we go that route, other similar candidates for consideration would include .env.test, .env.ci, .env.dev, .env.development, .env.stg, .env.staging, .env.prod, and .env.production.

I suppose something like .env.* does not work here?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose something like .env.* does not work here?

No.

- .profile
- .textmate_init
- .zlogin
Expand Down