`cml pr`: Merging the P.R. with `Create a merge commit` option ignores `skip c.i.`
See original GitHub issueWhen merging a P.R. created by cml pr
, if the option Create a merge commit
is selected from the GitHub interface a new commit is added.
This triggers the C.I. on the base branch, ignoring the skip c.i.
in the CML commit message.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (6 by maintainers)
Top Results From Across the Web
`cml pr`: Allow users to configure P.R. title / description · Issue ...
cml pr : Allow users to configure P.R. title / description #792 ... cml pr : Merging the P.R. with Create a merge...
Read more >Merge request pipelines - GitLab Docs
Create a new merge request from a source branch with one or more commits. Push a new commit to the source branch for...
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
Here are 7 tricks with github actions that changed my life (or at least my CI/CD pipeline). These tricks helped me create a...
Read more >Azure DevOps Pipeline not triggering when merge-commit ...
If we do not add the [skip ci] when we submit from develop branch, the CI for main branch will be triggered after...
Read more >GitHub Pull Request Builder - Jenkins Plugins
Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Or #792 + example in docs for this case 👼
Should we include
[skip-ci]
in the pull/merge request title?