-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
[Feat]: Ability to sync towards most recent semver release #547
Comments
Hi @JakobHavtorn , |
@all-contributors please add @JakobHavtorn for idea |
I've put up a pull request to add @JakobHavtorn! 🎉 |
Signed-off-by: Andy Augustin <[email protected]>
@JakobHavtorn sorry for delay. At least I have a PR available to sync the tags (first step). #561 on:
# manual trigger
workflow_dispatch:
jobs:
repo-sync:
runs-on: ubuntu-latest
# https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
permissions:
contents: write
pull-requests: write
steps:
# To use this repository's private action, you must check out the repository
- name: Checkout
uses: actions/checkout@v4
- name: actions-template-sync
uses: AndreasAugustin/actions-template-sync@feat/547_tags # reference the branch
with:
source_repo_path: <owner/repo>
upstream_branch: <target_branch> # defaults to main
is_with_tags: true # new property |
Signed-off-by: Andy Augustin <[email protected]>
Describe the feature
Always syncing to the most recent commit to
main
is useful, but in some release schedules, several PRs might be accumulated inmain
before a new release is made. Being able to sync towards the most recent release (as measured by semantic versioning) would be a good way to make the synchronisation even more structured. It would also be very useful to have an Action variable that contains the release notes for the release tag we are syncing against, so these notes can be included in the PR description.Use Case
This would enable
Proposed Solution
I imagine the implementation would consist of steps similar to:
*.*.*
).main
, as before.Acknowledgements
The text was updated successfully, but these errors were encountered: