Revert "Remove 'main' branch from release workflow triggers (#115)"

[Dargon789]

This reverts commit 21b6cc1.

Summary by Sourcery

CI:

• Re-enable the release workflow to run on pushes to the main branch in addition to master.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Reverts a previous workflow change by re-adding the main branch to the GitHub Actions release workflow trigger so releases run on both master and main pushes.

Flow diagram for release workflow branch filtering

flowchart TD
  PushEvent[PushEvent] --> CheckBranch[CheckBranch]
  CheckBranch -->|branch is master| RunReleaseWorkflow[RunReleaseWorkflow]
  CheckBranch -->|branch is main| RunReleaseWorkflow
  CheckBranch -->|branch is other| IgnoreEvent[IgnoreEvent]

Loading

File-Level Changes

Change	Details	Files
Re-enable release workflow execution on pushes to the main branch alongside master.	Update GitHub Actions workflow trigger configuration to include the main branch in the push branches list Preserve existing concurrency settings and other workflow behavior unchanged	.github/workflows/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
🔚	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[Dargon789]

@Mergifyio update

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[mergify]

update

❌ Base branch update has failed

Details

Repository rule violations found

Cannot update this protected ref.

This branch must not contain merge commits.

Changes must be made through a pull request.

2 of 2 required status checks are expected.

Code scanning is waiting for results from CodeQL for the commit b6aa2c5. Existing alerts might have been detected because the code changes were too large.

Commits must have verified signatures.

[Dargon789]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed