Relax PR approval requirement for previous collaborators

Open
  • Is something wrong?
#33 2 comments 0 reactions 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, rust
Domain
ci-cd

Research direction

Start by locating the bot's PR approval requirement and researching whether the GitHub API exposes previously merged PRs by author. The work is done when the bot can run for an author whose earlier PR was merged, with the existing approval behavior otherwise preserved.

Written by the indexing model from the issue text.

Description

An idea from djc in discord:

In fact it would be nice if we can relax it even more, like allow the bot to run if we previously merged a PR from the same author

This will probably be a little bit trickier than #32 - I'm not sure if GitHub exposes this state through the API. Some research will be required.

Dominant language
Rust
Stars
13
Forks
3
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 rustls/rustls-bench-app

All issues in rustls/rustls-bench-app

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.