[Feature Request] Do not close PRs that have auto-merge activated

Open
#1,096 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd, devops

Research direction

Start by tracing the stale bot's pull-request closing path and how it could detect whether auto-merge is enabled; the issue names no file or test entry point. Done means an auto-merge-enabled PR remains open and receives the proposed explanatory comment, while ordinary stale PR behavior is preserved.

Written by the indexing model from the issue text.

Description

feature request

Description:
If a PR is enabled for auto-merge, then stale bot should never close the PR. Stale bot could add a comment to the PR saying that the PR is stuck in the auto-merge process.

Justification:
Auto-merge is a convenient feature to merge PRs without waiting for the completion of a long CI run. However, if a CI test fails unexpectedly (e.g. because of flakiness), then the PR would never turn green and consequently auto-merge would not perform the merge. After some time the stale action would close the PR.

However, I believe PRs that have auto-merge activated should never be closed automatically because there was already a serious intention to merge the PR.

/cc @leonor-loureiro @dkunkler

Dominant language
TypeScript
Stars
1.7k
Forks
438
Avg merge
27d 8h
Merged PRs (30d)
1

Getting set up

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.

More from actions/stale

All issues in actions/stale

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.