Skip to content

fix: add 'skipPipeline' configuration option to perform the backmerge without CI/CD Pipeline #70

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JustC0des
Copy link

To avoid running the CI/CD pipeline on the target branch a new configuration option 'skipPipeline' has been added.
This prevents the CI/CD Pipeline from being triggered in the target branch to avoid e.g. automatic merge requests created in the CI/CD pipeline from being created without any proper changes.

  [
      "@saithodev/semantic-release-backmerge",
      {
        "backmergeBranches": [{from: "prd", to: "qas"}],
        "skipPipeline": true
      }
    ]
  ]

… without triggering the CI/CD pipeline on the target branch
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.

1 participant