You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I have a mergify config where I am trying to use mergify to approve my PRs after status checks success and I am attempting to have renovate raise PRs for each individual dependency. Mainly GitHub Action dependencies and npm dependencies. I was thinking of putting the PRs from renovate into a merge queue so that they can be merged one by one sequentially. Right now, the max number of PRs that renovate should be raising at one time should be about 3: the default 2 plus if I happen to trigger a major dependency update in the dashboard.
Ideally, I would like for each PR in the queue to wait until they are in position 0 of the queue and then trigger a rebase from renovate. This way, renovate doesn't leave and comment about someone interrupting the PR and is still prepared to update itself should something else crop up that can be grouped with the PR. For example, nodejs don't release on docker hub at the same time as they make a new release.
I was wondering whether there was anyway to tell mergify to not merge or rebase a commit from the base/main branch even when the PR is in position 0 of the queue and Renovate might take considerably longer to rebase a PR. Below is where I've got to with my mergify config:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. I have a mergify config where I am trying to use mergify to approve my PRs after status checks success and I am attempting to have renovate raise PRs for each individual dependency. Mainly GitHub Action dependencies and npm dependencies. I was thinking of putting the PRs from renovate into a merge queue so that they can be merged one by one sequentially. Right now, the max number of PRs that renovate should be raising at one time should be about 3: the default 2 plus if I happen to trigger a major dependency update in the dashboard.
Ideally, I would like for each PR in the queue to wait until they are in position 0 of the queue and then trigger a rebase from renovate. This way, renovate doesn't leave and comment about someone interrupting the PR and is still prepared to update itself should something else crop up that can be grouped with the PR. For example, nodejs don't release on docker hub at the same time as they make a new release.
I was wondering whether there was anyway to tell mergify to not merge or rebase a commit from the base/main branch even when the PR is in position 0 of the queue and Renovate might take considerably longer to rebase a PR. Below is where I've got to with my mergify config:
Beta Was this translation helpful? Give feedback.
All reactions