Webhook deployments from git commits should respect [skip ci] #4358
Replies: 7 comments 1 reply
-
|
Not resolved at v4.0.0-beta.416 as well. |
Beta Was this translation helpful? Give feedback.
-
|
Yes please! |
Beta Was this translation helpful? Give feedback.
-
|
This would be really great, yes. |
Beta Was this translation helpful? Give feedback.
-
|
good idea ! |
Beta Was this translation helpful? Give feedback.
-
|
First, thank you so much for Coolify and all the brilliance that goes into this platform. I love it and it's a real blessing. Second, yes this would be a wonderful feature. |
Beta Was this translation helpful? Give feedback.
-
|
This would be really great to have! But I would recommend doing this how Netlify does it: https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/
|
Beta Was this translation helpful? Give feedback.
-
|
+1 it's not nice to have a bunch of deployments auto-triggered by e.g. changelog updates and other automated stuff |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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
Beta Was this translation helpful? Give feedback.
All reactions