- Notifications
You must be signed in to change notification settings - Fork1.2k
Release process update#588
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
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.
Pull Request Overview
This PR updates the release process and development workflow by providing clearer guidelines for contributors and automating branch synchronization and release creation via GitHub workflows.
- Updated CONTRIBUTING.md to instruct contributors to target the next branch for pull requests.
- Added a new workflow (sync-next-branch.yml) to automatically keep the next branch synchronized with main.
- Introduced a release workflow (release.yml) along with additional workflows (pr-base-check.yml and docker-publish.yml) to enforce branch targeting and streamline releases.
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| CONTRIBUTING.md | Instructs contributors to open PRs against the next branch. |
| .github/workflows/sync-next-branch.yml | Automates daily sync of the next branch with main. |
| .github/workflows/release.yml | Automates release creation with tag validation, branch checks, and PR creation. |
| .github/workflows/pr-base-check.yml | Adds a reminder comment to PRs targeting main to switch to the next branch. |
| .github/workflows/docker-publish.yml | Extends Docker publish triggers to include changes from the next branch. |
Comments suppressed due to low confidence (1)
.github/workflows/pr-base-check.yml:27
- The inline markdown formatting in this comment contains extra underscores that may lead to unintended emphasis. Consider revising the syntax (e.g., using proper bold or italic markdown) so that the message renders clearly.
__If this is a bug fix that requires a patch release __ (e.g., a critical bug that needs to be fixed before the next release)__, please leave the base branch as \`main\`.__20ddb93 to4305a77Compare👋 Hi there! It looks like this PR is targeting the If this is a bug fix that requires a patch release __ (e.g., a critical bug that needs to be fixed before the next release), please leave the base branch as You can change this by:
Thanks for your contribution! 🚀 |
b9a5f2c intomainUh oh!
There was an error while loading.Please reload this page.
Closes: