PR Dashboard: stop using Outdated as an implicit reason to route thread back to reviewer

Open
#109 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
ci-cd

Research direction

Start by reading issue #26 and locating the PR Dashboard implementation that routes review threads. Confirm how "Outdated" currently triggers routing, then change the behavior so only an explicit reply or explicit discussion resolution routes a thread back to the reviewer. Done means outdated status alone no longer causes that routing and the relevant workflow checks pass.

Written by the indexing model from the issue text.

Description

After implementing

We could consider removing "Outdated" as being an implicit reason to route thread back to reviewer and instead require an explicit reply (or explicit resolve discussion).

Dominant language
JavaScript
Stars
7
Forks
23
Avg merge
15h 46m
Merged PRs (30d)
41

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 open-telemetry/shared-workflows

All issues in open-telemetry/shared-workflows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.