The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
- Community
- Q&A
- Atlassian Automation
- Questions
- How to force trigger pipeline for tags with last commit containing [skip ci]?
How to force trigger pipeline for tags with last commit containing [skip ci]?
Michael Brizic
July 1, 2021 edited
A commit was made that contained [skip ci]. Then, a branch was created from this commit. Next, a tag was created from this branch.
There is a pipeline that monitors for new tags and builds them.
However, the pipeline doesn't trigger due to the last commit containing [skip ci].
Is there a good pattern for overriding this so that the tags pipeline triggers?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Atlassian Community Events
Copyright © 2026 Atlassian