quarkusio / quarkusio/quarkus-github-bot

Schedule to merge after all checks are ok

Open
#28 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
30
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Just like @dependabot merge, I think it would come in very handy to let the bot merge a PR once all checks are green (and the PR is still mergeable).

First I thought that triage/waiting-for-ci should be added automatically, but now I'm not so sure about that.
Maybe better add something like merge-pending or similar?
In any case, if a label is added, it should be auto-removed after the merge.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing @dependabot merge handling and how the bot checks PR mergeability and labels. Define the scheduling and label behavior before locating the relevant implementation and tests; done means a marked PR merges automatically only after all checks pass, remains mergeable, and any temporary label is removed after merging.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, java
Domain
ci-cd, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.