docs: Add troubleshooting guide for the scenario that release PR is merged with autorelease:closed
#2255
+3
−0
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
suztomo
reviewed
Mar 29, 2024
| @@ -107,3 +107,6 @@ more API calls (which is one reason a manifest config is preferred). | |||
| 3. Iterate through the latest tags and compare against commit | |||
| SHAs seen in the last 250 commits on the branch. This is to | |||
| ensure that the tag happened on this target branch. | |||
|
|
|||
| ### What if my release PR is merged with `autorelease:closed`? | |||
There was a problem hiding this comment.
This heading is the cause of a problem "Why does my merged release pull request not trigger the release job?"
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.
No description provided.