Uses service account token when cherry-picking #2752
Merged
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
ncordon
added
bug
to-cherry-pick
neo4j-oss-build
pushed a commit
that referenced
this pull request
Apr 14, 2022
ncordon
added a commit
that referenced
this pull request
Apr 14, 2022
neo4j-oss-build
added a commit
that referenced
this pull request
Apr 14, 2022
ncordon
pushed a commit
that referenced
this pull request
Apr 14, 2022
neo4j-oss-build
added a commit
that referenced
this pull request
Apr 14, 2022
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.
This was approved in #2741 but it had to be reverted due to an external problem with the actions and a new version of
git. This should have been solved by #2751 (see that PR for more context).What
Uses a personal access token for the service account https://github.com/neo4j-oss-build when cherry picking.
Why
That should trigger the CI for us automatically when creating the automatic cherry-picks PR, according to the solutions proposed in peter-evans/create-pull-request#48, contrary to what's happening at the moment.