Bump backport to 6.1.1 #122119
Merged
Bump backport to 6.1.1 #122119
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
sorenlouv
added
backport:skip
sorenlouv
force-pushed
the
bump-backport-6.0.0
branch
from
fa1b4ba to
48c4ef5
Compare
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
This was referenced Jan 5, 2022
Merged
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.
Upgrades
backportto v6.1.1Changelog
Add support for multiple
pathproperties (sorenlouv/backport#273)This feature makes it possible to list commits that only touch certain files. This is useful in monorepos where many developers work on different projects within a single repo.
Or via the config file:
{ "commitPaths": ["my/project1", "my/project2"] }Show hint about missing backports (sorenlouv/backport#276, sorenlouv/backport#282)
Sometimes it is not possible to backport a change cleanly due to conflicts. In many cases the conflicts are caused by missing backports. It is often easier and safer to perform the missing backports than manually resolving the conflict. To help the user do this the backport tool will now suggest what is causing the conflict, and which backports are missing.
Details view (sorenlouv/backport#277)
The new details view shows the usual interactive list view but with a little more info and clickable links, enabling the user to jump straight to existing pull requests.
Add
--revieweroption (sorenlouv/backport#280)This option makes it possible to request a review when creating the backport:
Add status comment to source pull request (sorenlouv/backport#281)
This will add a comment to the source pull request (the pull request that was backported) to indicate the resulting backport pull requests.
Other changes: