ci: [Backport] Temporarily disabled trigger for release automation #3835
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
commented out the weekly trigger for release preparation
michalChrobot
requested review from
a team,
EmandM and
NoelStephensUnity
as code owners
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.
Purpose of this PR
This is a backport of #3829
This PR temporarily disables the trigger for release preparation. This is done since I have changes in #3828 (After that land I will backport this here) that I would like people to verify that would modify the behavior of this action. Per schedule next release would be next week and because of holidays we moved our schedule by 1 week so running this now could fail again/cause problem about reverting commit on main branch (issue described in linked PR)
So given this I will disable it here and re-enable it from the linked PR when changes are properly reviewed
Jira ticket
N/A
Documentation
N/A
Testing & QA (How your changes can be verified during release Playtest)
N/A
Backports
This is a backport of #3829