Skip to content

New strategy to trigger release? #714

@eunjae-lee

Description

@eunjae-lee

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".

This might solve issues like #667

Is there any side effect?

Should it become a default behavior? or an opt-in feature?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions