Skip to content
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

Tagging not working if last commit in target branch has "skip ci" #3606

Closed
3 tasks done
xoxys opened this issue Apr 10, 2024 · 1 comment · Fixed by #3612
Closed
3 tasks done

Tagging not working if last commit in target branch has "skip ci" #3606

xoxys opened this issue Apr 10, 2024 · 1 comment · Fixed by #3612
Labels
bug Something isn't working forge/github github forge related

Comments

@xoxys
Copy link
Member

xoxys commented Apr 10, 2024

Component

server

Describe the bug

If the last commit in e.g. the main branch has skip ci in its commit message, creating a tag on top of that commit does not trigger the CI as it results in an empty pipeline.

System Info

version	"next-6a6cb094fb"

Additional context

No response

Validations

  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
@xoxys xoxys added the bug Something isn't working label Apr 10, 2024
@xoxys
Copy link
Member Author

xoxys commented Apr 14, 2024

Cant reproduce this behavior with Gitea as Gitea is using something like created tag v0.4.0 as pipeline.Message on tag event while on GitHub pipeline.Message is the commit message of the head commit for tag events.

@xoxys xoxys added the forge/github github forge related label Apr 14, 2024
lafriks pushed a commit that referenced this issue Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working forge/github github forge related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant