Stale issue workflow runs even on issues with linked PRs

Open Beginner friendly
  • Is something wrong?
#7,341 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd

Research direction

Start in the repository's .github/workflows/ directory and find the workflow that runs the stale-issue action. Read its schedule, the actions/stale step, and any conditions around assignees; the goal is to skip assignee tagging when an issue has a linked pull request. Check how the workflow currently detects linked PRs or whether it needs a condition or an additional API step, then verify the updated workflow in a dry run or a test branch. Done means the stale workflow no longer tags assignees on issues with linked PRs while still handling genuinely stale issues.

Written by the indexing model from the issue text.

Description

good first issue

We've a lot of PRs to review and merge. Assignees shouldn't be tagged if the reviews are delayed at our end

Dominant language
Kotlin
Stars
1.2k
Forks
1.4k
Avg merge
1d 23h
Merged PRs (30d)
151

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 commons-app/apps-android-commons

All issues in commons-app/apps-android-commons

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.