Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add a new release workflow #578

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add a new release workflow #578

wants to merge 1 commit into from

Conversation

SamMorrowDrums
Copy link
Collaborator

  • Updates advice to contributors to merge PRs to next branch
  • Adds automation to complain about merging to main.
  • Adds a release publishing workflow

@Copilot Copilot AI review requested due to automatic review settings June 25, 2025 10:10
@SamMorrowDrums SamMorrowDrums requested a review from a team as a code owner June 25, 2025 10:10
@github-actions GitHub Actions
Copy link

👋 Hi there!

It looks like this PR is targeting the main branch. To help maintain our development workflow, please change the base reference to next instead.

You can change this by:

  1. Clicking the "Edit" button next to the PR title
  2. Changing the base branch from main to next
  3. Clicking "Update pull request"

Thanks for your contribution! 🚀

Copilot
Copilot AI reviewed Jun 25, 2025
View reviewed changes
Copy link
Contributor

@Copilot Copilot AI left a 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 introduces a structured release workflow, enforces targeting the next branch for contributions, and extends Docker publishing triggers.

  • Updated contributing guidelines to direct PRs to the next branch.
  • Added a workflow to block PRs against main and prompt authors to switch to next.
  • Introduced a manual release workflow (.github/workflows/release.yml) for tag validation, rebasing, tagging, PR creation, and a summary.
  • Extended docker-publish.yml to run on both main and next branches.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
CONTRIBUTING.md Added admonition and updated PR submission step to target next.
.github/workflows/release.yml New release workflow for validating inputs, rebasing, tagging, PR creation, and summary.
.github/workflows/pr-base-check.yml Workflow to comment on PRs targeting main, asking to switch to next.
.github/workflows/docker-publish.yml Extended Docker publish triggers to include the next branch.
Comments suppressed due to low confidence (2)

.github/workflows/release.yml:68

  • After successfully rebasing next onto main, the workflow never pushes the updated next branch back to the remote. Add a git push --force-with-lease origin next step to ensure the PR includes the rebased commits.
            echo "rebase-success=true" >> $GITHUB_OUTPUT

.github/workflows/release.yml:134

  • The workflow waits for a draft release to appear but never creates one. Introduce a step (e.g., gh release create --draft "$TAG") or use an official action to generate the draft release after tagging.
          echo "Waiting for GitHub to create the draft release..."

@SamMorrowDrums SamMorrowDrums force-pushed the release-process-update branch from e7504a5 to 48817ed Compare June 25, 2025 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

Copilot code review Copilot Copilot left review comments

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@SamMorrowDrums