-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
chore(ci): reuse changelog workflow #11549
Conversation
75fd656
to
a8a53fb
Compare
a8a53fb
to
c5f58fc
Compare
c5f58fc
to
719da3d
Compare
14bcbc1
to
8ab107a
Compare
@vm-001 is this up to date? It seems we have done more changes to the changelog process |
b476a1a
to
592f161
Compare
Yes, this one is up to date. Need the relying one be merged first: https://github.com/Kong/gateway-changelog/pulls |
592f161
to
ba4918e
Compare
e05d9ae
to
46d9216
Compare
46d9216
to
727258a
Compare
727258a
to
2df56d0
Compare
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.2.x release/3.2.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.2.x
# Create a new branch
git switch --create backport-11549-to-release/3.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 710489f2d4cdbebf0fa8c9b9f8e2d8e38e749cad
# Push it to GitHub
git push --set-upstream origin backport-11549-to-release/3.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.3.x release/3.3.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.3.x
# Create a new branch
git switch --create backport-11549-to-release/3.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 710489f2d4cdbebf0fa8c9b9f8e2d8e38e749cad
# Push it to GitHub
git push --set-upstream origin backport-11549-to-release/3.3.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.3.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.4.x release/3.4.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.4.x
# Create a new branch
git switch --create backport-11549-to-release/3.4.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 710489f2d4cdbebf0fa8c9b9f8e2d8e38e749cad
# Push it to GitHub
git push --set-upstream origin backport-11549-to-release/3.4.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.4.x Then, create a pull request where the |
This avoids code duplication and makes improvements on changelog generation/format easier.
…11668) * chore(changelog): use reusable changelog workflow (#11549) This avoids code duplication and makes improvements on changelog generation/format easier. * chore(changelog): use simpler format for changelog files with the new (#11652) changelog generator The new changelog generator removes the need to write down jiras or prs manually. Now these are automatically extracted by the script and these fields are no longer needed. Also, we changed the file extension to .yml to stay consistent with the rest of the repository. Existing changelogs were modified automatically using yq to remove these fields that are no longer needed. This will be eventually backported to all branches that currently uses the new changelog generator. KAG-2545 --------- Co-authored-by: Yusheng Li <[email protected]> Co-authored-by: Datong Sun <[email protected]>
Summary
To avoid redundant work, I moved all the changelog tools to a separate repo gateway-changelog. All the release branches can reuse the shared GitHub action to validate the changelog schema.
changelogs: