Repository navigation
Report backport results by target branch - #258
Merged
Merged
Conversation
Contributor
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success235 tests passing in 20 suites. Report generated by 🧪jest coverage report action from e18de75 |
Member
Author
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
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.


Summary
Closes #145. Log a final result for each target branch, including its error when a backport fails. Previously the final error listed failures without their target branches. Previously reported failures that prevent a retry are shown as skipped. Existing failure comments and process exit behavior are preserved. GitHub Actions also writes a job summary with links to created or existing backport pull requests and expandable failure details.
For example, the log report looks like:
OKincludes dry runs and branches with nothing new to push. Multiline errors continue beneath the error column.The GitHub Actions job summary renders a table like this:
Failure details appear in expandable sections below the table.
Validation
npm test -- --runInBand(235 tests passed)npm run compilenpm run lint