-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create centralised backport
workflow
#17
Create centralised backport
workflow
#17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested via dummy PR in test repo that backported successfully (via JackPGreen2/hz-docs#26).
From what I see in https://github.com/JackPGreen2/hz-docs/actions/runs/12029776846/job/33535776479 the action was skipped in all cases.
Fixed link. |
bada218
to
7755724
Compare
70180ae
to
c92f1af
Compare
3987032
to
23f82cb
Compare
…8] (#1396) In [DOC-255](https://hazelcast.atlassian.net/browse/DOC-255), branch protection was added - preventing direct `push`es. Instead, the backport workflow should create PRs to backport the changes. This gives the _possibility_ for pre-merge checks to be run (i.e. preventing introducing dead links etc). Leverages [_existing_ `backport` tool](https://github.com/hazelcast/backport), but exposed some issues which need to be addressed **before this can be merged**: - hazelcast/backport#14 - hazelcast/backport#15 - hazelcast/backport#16 - hazelcast/backport#17 Tested in a [test repo](https://github.com/JackPGreen2/hz-docs), where a [dummy PR](JackPGreen2#5) was [successfully backported](JackPGreen2#16). However, due to the complexity of fork-triggering, it wil need to be re-tested once merged. Fixes: [DOC-268](https://hazelcast.atlassian.net/browse/DOC-268) [DOC-255]: https://hazelcast.atlassian.net/browse/DOC-255?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [DOC-268]: https://hazelcast.atlassian.net/browse/DOC-268?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Following hazelcast#17, [backport PRs are being raised by `github-actions`](hazelcast/hazelcast-mono#3669), rather than using the specified `GH_TOKEN`
Following #17, [backport PRs are being raised by `github-actions`](hazelcast/hazelcast-mono#3669), rather than using the specified `GH_TOKEN`.
To support
backport
being used in multiple GitHub Actions:A composite GitHub Action has been created to centralise it's usage, to make callers simpler.
Implementation is a sliced from
hazelcast-mono
, with some parameters now explicit inputs.Tested via dummy PR in test repo that backported successfully (via JackPGreen2/hz-docs#26).