chore: Reverted last release attempt to see about fixing the automation run #3821
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
michalChrobot
requested review from
a team,
EmandM and
NoelStephensUnity
as code owners
michalChrobot
deleted the
revert-changes-to-run-release-automation-again
branch
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 PR aims to (one time action in our current case)
This is done to test Release Automation and any flaws related to it + there were some PRs that we wanted to backport either way so it makes sense to just "regenerate" the release branch
Jira ticket
N/A
Documentation
N/A
Testing & QA (How your changes can be verified during release Playtest)
N/A
Backports
N/A, only related to NGOv2.X (
develop-2.0.0branch)