refactor: 💡 Clean up release triggers #2602
Open
+0
−59
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
DhariniJeeva
approved these changes
Dec 2, 2024
cameronperera
approved these changes
Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Clean up release triggers we do not use.
test-release-trigger: this trigger is not used, since to launch any test run we do it directly within boundary-deskto-releases, here documentation about it.build-artifacts-for-testing-trigger: I never used this trigger and looking at its history usage, seems not used, aside from some test runs we did onyarn-upgradetesting, until we start manually triggering those fromboundary-desktop-releases.🎟️ Jira ticket