We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
List pull requests associated with commit
For now, the condition to trigger release is
correctCommitMessage && correctBranch
(https://github.com/algolia/shipjs/blob/master/packages/shipjs-lib/src/lib/config/defaultConfig.js#L88-L107)
What if it becomes
(correctCommitMessage || prLabeled) && correctBranch
prLabeled here means if the PR associated with the latest commit message has a specific label like "release:trigger".
prLabeled
This might solve issues like #667
Is there any side effect?
Should it become a default behavior? or an opt-in feature?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
List pull requests associated with commit
For now, the condition to trigger release is
(https://github.com/algolia/shipjs/blob/master/packages/shipjs-lib/src/lib/config/defaultConfig.js#L88-L107)
What if it becomes
prLabeled
here means if the PR associated with the latest commit message has a specific label like "release:trigger".This might solve issues like #667
Is there any side effect?
Should it become a default behavior? or an opt-in feature?
The text was updated successfully, but these errors were encountered: