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.
The proposed workflow here is:
byte-buddy-tag
I had to make the assumption that the pr is opened from a fork owned by the committer, because pull_request actions don't seem to 'know' the forked repo name.
I also don't know if the bot will actually have permissions to push to the branch... Although I've set them to
on the new action, these settings will not take effect until after the pr is merged, so the job is currently running with
-- these permissions are clearly not enough to push. I have kinda tested it against myself here and it seems to work, but whether it will in practice will depend on whether
Allow edits and access to secrets by maintainers
also grants the power to push to bots... To really ensure this worked, I think I'd need to fiddle about with branches on kanela... 🤔 Alas I have not those permissions...Edit: Ok I got someone to test this flow for me by pr-ing to my branch, but the bot doesn't have permissions to push, so this approach won't work. Back to the drawing board...