Jul 20, 2022 · I'm looking on a way to trigger a Azure pipeline ONLY on successful (or attempted) pull request merge. There is no such out of box way to achieve this at this moment.

Jul 22, 2024 · I am trying to use the Create PR task in a pipeline to merge changes from my source branch to target branch (master). I want to bypass the policies of having reviewers and …

Dec 17, 2024 · I have found some articles that said you need to create the PR, then update it. However, the serverless agent doesn't allow for me to get the created PR id and then update it …

Learn how to use merge request pipelines in GitLab CI/CD to test changes efficiently, run targeted jobs, and improve code quality before merging.

Apr 17, 2020 · Azure Devops doesn't have the option to control which branch can be merged into master, but we can use branch policies as a workaround. Here's my working direction:

You should have a pipeline running on each PR that just runs the tests, then merging to master (or main, which is the preferred name now) should build the artifacts and deploy.

Mar 20, 2023 · - The issue is that after merging a PR on master, both master and release_branch pipelines will be triggered and both will run under the X.yml that exists on master.

Mar 24, 2018 · My problem is that I thought master branch was protected by pipelines as job was configured on master only and option 'Only allow merge requests to be merged if the pipeline …

Dec 17, 2023 · If there are pull requests againt master, I want to ensure that the pipeline only runs after pull requests are merged into the master branch and not before the pull request is …

If you plan to merge to Master from areas other than the develop branch, I just want to call out that the PR which will be automatically created by deploy/build could have conflicts and …