Suppress "deployed to test-trigger-is" items on the PR timeline#5927
Merged
Conversation
The test-trigger-is environment exists only to gate the secrets used to trigger integration tests, not to track a real deployment. Referencing it made every PR and merge-group run post a "deployed to test-trigger-is" item on the pull request timeline. Set deployment: false so the jobs still get the environment's secrets and protection rules but no deployment object is created. Co-authored-by: Isaac
janniklasrose
approved these changes
Jul 15, 2026
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.
The
test-trigger-isenvironment exists only to gate the secrets used to trigger integration tests, not to track a real deployment. Referencing it made every PR and merge-group run post a "deployed to test-trigger-is" item on the pull request timeline.Set
deployment: falseso the jobs still get the environment's secrets and protection rules but no deployment object is created.This pull request and its description were written by Isaac.