[nrf noup] ci: enable custom base for manifest-PR
#2170
Merged
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
Contributor
|
@thst-nordic Looks that the branch needs an update? It seems that it was based on main |
Contributor
Author
|
yes, I changed the base in GH web gui, but I'll fix commits. |
new arg base-branch defaults to main, but can map zephyr release branch to nrf release base Signed-off-by: Thomas Stilwell <thomas.stilwell@nordicsemi.no>
thst-nordic
force-pushed
the
release-manifest-pr
branch
from
73a8ec8 to
4bbab43
Compare
rlubos
approved these changes
Oct 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
new arg base-branch defaults to main,
but can map zephyr release branch to nrf release base
tested here: nrfconnect/sdk-zephyr-testing#17