We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
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
For CIs it has been established as a standard to be able to put [skip ci] somewhere in a commit message to tell the CI to not run with this commit.
[skip ci]
I noticed earlier that deployments by webhook for, in my case, Github pushes still trigger deployments in Coolify.
I think they should be skipped when [skip ci] is found in the commit message.
It's also ok to introduce another keyword.
No response
v4.0.0-beta.370
No (self-hosted)
Ubuntu 22.04.5 LTS
The text was updated successfully, but these errors were encountered:
This is more of an improvement request as it has not yet been implemented, so I am moving this to a GitHub discussion.
Sorry, something went wrong.
No branches or pull requests
Error Message and Logs
For CIs it has been established as a standard to be able to put
[skip ci]
somewhere in a commit message to tell the CI to not run with this commit.I noticed earlier that deployments by webhook for, in my case, Github pushes still trigger deployments in Coolify.
I think they should be skipped when
[skip ci]
is found in the commit message.It's also ok to introduce another keyword.
Steps to Reproduce
[skip ci]
in the commit messageExample Repository URL
No response
Coolify Version
v4.0.0-beta.370
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 22.04.5 LTS
Additional Information
No response
The text was updated successfully, but these errors were encountered: