Block .env updates #1
Merged
Conversation
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
quekshuy
force-pushed
the
quekshuy/block-env-updates-workflow/1
branch
from
1b48291 to
e0bb3df
Compare
quekshuy
requested review from
a team,
daryllxd,
julianalmandos,
nvdai2401 and
strawhatduckk
and removed request for
a team
strawhatduckk
approved these changes
Nov 6, 2025
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.
What
This pull request introduces a new GitHub Actions workflow to help protect the
.envfile from accidental or unauthorized changes during development. The workflow automatically checks for changes to.envin pull requests and blocks them if detected.Workflow automation:
.github/workflows/block-env-updates.ymlto automatically fail pull requests that add, modify, or rename the.envfile using a custom GitHub Actions script.Why
For security reasons, we'd prefer if no one accidentally adds org keys to this public repo.
For efficiency reasons (of getting our proposed changes into the mainline), we didn't make this repo a private mirror and instead went with the public fork.
A required check is one of the best compromises (and we can expand it to ensure that no commit actually changes
.envinstead of just requiring it at a per-PR level).