Skip to content
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

BACKLOG-23588: Update release workflow #134

Merged
merged 1 commit into from
Mar 7, 2025
Merged

Conversation

rknj
Copy link
Contributor

@rknj rknj commented Jan 24, 2025

No description provided.

@rknj rknj requested a review from Fgerthoffert January 24, 2025 11:08
@Fgerthoffert Fgerthoffert merged commit 2e0cbf5 into master Mar 7, 2025
8 of 9 checks passed
Copy link

github-actions bot commented Mar 7, 2025

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "BACKLOG-23588: Update release workflow". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Sample valid messages:

A PR introducing a breaking change(!)

feat!: send an email to the customer when a product is shipped

A regular commit

docs: correct spelling of CHANGELOG

This message will be deleted once the PR title conforms with the convention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants