Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assign reviewers #53

Closed
Bullrich opened this issue Aug 23, 2023 · 0 comments · Fixed by #97
Closed

Assign reviewers #53

Bullrich opened this issue Aug 23, 2023 · 0 comments · Fixed by #97
Assignees

Comments

@Bullrich
Copy link
Contributor

Add the ability to assign users & reviewers.

@Bullrich Bullrich added this to the Project launch milestone Aug 23, 2023
@Bullrich Bullrich self-assigned this Aug 23, 2023
@Bullrich Bullrich removed this from the Project launch milestone Sep 5, 2023
Bullrich added a commit to paritytech/polkadot-sdk that referenced this issue Sep 28, 2023
Created a Github Action that uses the [Review-Bot
app](https://github.com/paritytech/review-bot) to require more fine
tuned requirements to review pull requests before allowing the PR to be
merged.

This uses
[`pull_request_target`](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target)
for the event, not `pull_request`. This is a security measure so that an
attacker doesn’t have access to the secrets.

All the rules have been copied from the original
`.github/pr-custom-review.yml` file.

I want to clarify, this particular commit is **not intended to replace
PRCR yet**.

# Advantages it brings over `PRCR`

Most of the features available in `PRCR` have been duplicated and
enhanced. For a complete detailed write up, please see:
- paritytech/pr-custom-review#114 -> Proposal for the rewrite
- [Review Bot
Documentation](https://github.com/paritytech/review-bot/blob/main/README.md)

The most important features are:
- `include` and `exclude` fields now accept an array, making it easier
to read the regular expressions.
- Ability to skip a rule
- We can set that PRs coming from a particular user or team will cause
the rule to be skipped.
- This is used in the `Audit rule`, which was requested by
@the-right-joyce.
  - This resolves paritytech/pr-custom-review#136
- Ability to request fellows instead of teams
- As requested in polkadot-fellows/runtimes#7, this bot has the ability
to request fellows by rank instead of users.
- We currently have polkadot-fellows/runtimes#31 which is using that
feature.

Aside from all the rules available in `PRCR` I have added a particular
rule to lock the review-bot files and require a review from the
`locks-review` team, the @paritytech/ci team and the
@paritytech/opstooling team to ensure that the file has been written
correctly.

## Next steps

The next steps will consist on paritytech/review-bot#53, once this issue
has been resolved, and `review-bot` has worked without any issues on
this repository for a while, we will upgrade it to be able to fully
replace `PRCR`.
Bullrich added a commit that referenced this issue Oct 30, 2023
Added the feature to request reviewers. For this we are using a github
app with pull request write permission (I need to request our app to be
updated).

I will be making a following PR to merge the keys as we are using the
same key for all the github classes.

The request feature is disabled by default.

Resolves #53

---------

Co-authored-by: Maksym H <1177472+mordamax@users.noreply.github.com>
@Bullrich Bullrich mentioned this issue Oct 31, 2023
Bullrich added a commit that referenced this issue Oct 31, 2023
This version includes the fix for #53 in #97
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant