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

Create a PR when automergeType=branch has not succeded for some time #30150

Open
rarkins opened this issue Jul 12, 2024 Discussed in #30145 · 0 comments
Open

Create a PR when automergeType=branch has not succeded for some time #30150

rarkins opened this issue Jul 12, 2024 Discussed in #30145 · 0 comments
Labels
core:automerge Relating to Renovate's automerge capabilities priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Jul 12, 2024

Discussed in #30145

Originally posted by schulzjo-tng July 12, 2024

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Bitbucket on-premise

Please tell us more about your question or problem

  • We would like to use Automerge on our Bitbucket project.
  • The default automergeType=pr is not viable for us because we require approvals for PRs, and Bitbucket neither supports self-approval nor an allow-list of users who can merge PRs without approval.
  • We have allowed the technical user to commit to the branch without PRs (that is supported, at least).
  • We have tried to use automergeType=branch which does work, but comes with another issue:
    • It can take weeks until a given branch is merged when there is a lot of activity on main, and nobody notices because Renovate only creates PRs when the pipeline fails.

Therefore, I was wondering if any of the following is possible:

  • Use the automergeType=branch strategy, but create a PR if no merge was possible for a given timeframe (e.g. 72 hours).
  • Use automergeType=pr, but commit the changes directly and close the PR instead of merging the PR via Bitbucket.

Thanks in advance for your help!

Logs (if relevant)

No response

@rarkins rarkins added type:feature Feature (new functionality) priority-4-low Low priority, unlikely to be done unless it becomes important to more people core:automerge Relating to Renovate's automerge capabilities labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core:automerge Relating to Renovate's automerge capabilities priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

1 participant