Skip to content

Conversation

@kivra-pauoli
Copy link
Contributor

⚠️ Disclaimer ⚠️ this is a Creative Friday initiative. A prior discussion around it might have not happened.

Motivation

Have no releases for no-release(fix): ..., for example.

Description

I recently merged with a message like no-release(deps): ... and this created an unwarranted release. This PR fixes that.

Copy link

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 fixes the CI workflow to prevent unwanted releases when commit messages start with no-release followed by a type in parentheses (e.g., no-release(deps):, no-release(fix):). Previously, only commits starting with no-release: (with a colon) would skip the release process, causing commits like no-release(deps): to trigger releases unintentionally.

Changes:

  • Updated the release job condition to check for no-release prefix instead of no-release: prefix

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Conventional Commits also allows for e.g.
no-release(<reason>): and we wanna account for that
without making this over-complicated
@kivra-pauoli kivra-pauoli enabled auto-merge (squash) January 23, 2026 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants