Skip to content

Allow _optional_ token to be provided#40

Merged
JackPGreen merged 1 commit into
hazelcast:masterfrom
JackPGreen:optional-token
Apr 13, 2026
Merged

Allow _optional_ token to be provided#40
JackPGreen merged 1 commit into
hazelcast:masterfrom
JackPGreen:optional-token

Conversation

@JackPGreen
Copy link
Copy Markdown
Contributor

When the github.token is used to create the backport, any subsequent action (e.g. one triggered on a new PR) is skipped due to GitHub workflow triggering rules.

To workaround this, we should allow the option to provide a non-bot token so GitHub thinks the PR is raised by a "real" user.

Slack discussion

Example execution (without token to prove it doesn't break existing).

@JackPGreen JackPGreen changed the title Allow optional token to be provided Allow _optional_ token to be provided Apr 13, 2026
@JackPGreen JackPGreen merged commit 023472f into hazelcast:master Apr 13, 2026
3 checks passed
@JackPGreen JackPGreen deleted the optional-token branch April 13, 2026 12:58
JackPGreen added a commit that referenced this pull request Apr 14, 2026
In #40, a token `input` added
- although it _technically works_, GitHub prevents you from actually
passing in a `secret` when you want to _use_ it, so in practice it's
useless:
<img width="482" height="572" alt="image"
src="https://github.com/user-attachments/assets/94907788-30fb-4a81-996e-5ea8bae92ce4"
/>

Updated to correctly define it as a `secret`.

Example execution:
- [with a valid token showing it actually
works](https://github.com/JackPGreen/backport-test/actions/runs/24395038764/job/71250635521)
- [with an invalid token showing it is actually using the token because
it fails to
authenticate](https://github.com/JackPGreen/backport-test/actions/runs/24395135078)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants