https://serverless-stack.com/ logo
Join Slack
Powered by
Is it possible to have seed wait for a bit before ...
# seed
g
Is it possible to have seed wait for a bit before deploying code that's merged? A lot of times we will merge like 5 prs at the same time but it will deploy the first as soon as it comes in so we have to wait for 2 deploys instead of 1.
a
It works like a queue.
g
I'm aware how it works, it's just not how I want it to work
a
Haha yeah.
Well but how you define “how much to wait”?
It’s just queing events.
Maybe there is a way to say “do not push this commit”.
Like based on the name or something.
g
What I basically really want is a merge queue where it waits until I am ready. Kind of like what github is working on but I dont have access to yet (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporat[…]-from-a-pull-request/adding-a-pull-request-to-the-merge-queue) 😅
a
I didn’t know they have that.
You want to manage the merge-queue, basically.
f
@Garret Harp would 
[skip-ci]
work better for you in this case?
So the first 4 prs when you merge, u add `[skip-ci]`in the comment.
a
@Frank that works for BBucket too? you mean adding a comment in the PR itself?
f
@Adrián Mouly so when u merge to master, in the commit msg if the phrase 
[skip-ci]
is detected, it would not trigger a deploy. And yeah that’d work for BB as well.
Hey guys, just wanted to let you know that you can now skip a build by including 
[skip ci]
or 
[ci skip]
in the commit message. @Garret Harp @Adrián Mouly
Open in Slack
PreviousNext
Powered by