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

PRCR - temporary disabled Audit rule #1239

Merged
merged 3 commits into from
Aug 29, 2023
Merged

PRCR - temporary disabled Audit rule #1239

merged 3 commits into from
Aug 29, 2023

Conversation

Bullrich
Copy link
Contributor

@the-right-joyce has requested to disable the Audit rule until we can fix the problem that it always request reviewers (even if the user belongs to the prevent-review-request field.

@Bullrich Bullrich added the R0-silent Changes should not be mentioned in any release notes label Aug 29, 2023
@paritytech-ci paritytech-ci requested review from a team August 29, 2023 08:17
Copy link
Contributor

@alvicsam alvicsam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think only this part can be commented:

      - min_approvals: 1
        teams:
          - srlabs

In this case it will require 2 distinct approvals from locks-review and polkadot-review teams for changes in paths:

  • polkadot/runtime/(kusama|polkadot|common)/*
  • polkadot/primitives/src/*.rs
  • substrate/primitives/*
  • substrate/frame/*

Excluding md files and weights.

@bkchr wdyt?

@paritytech-ci paritytech-ci requested a review from a team August 29, 2023 08:29
@bkchr
Copy link
Member

bkchr commented Aug 29, 2023

Neither polkadot-review or locks-review should be required for general changes in FRAME. Before this was only required for changes to the Polkadot/Kusama runtime. This means, these checks are useless any way as we will move these runtimes out to the fellowship. So, we probably should only keep locks-review and they can operate on the entire code base for when "locked" code is changed.

@juangirini
Copy link
Contributor

In this case it will require 2 distinct approvals from locks-review and polkadot-review teams for changes in paths:

  • polkadot/runtime/(kusama|polkadot|common)/*
  • polkadot/primitives/src/*.rs
  • substrate/primitives/*
  • substrate/frame/*

How important is to have a review from locks-review and polkadot-review on substrate/frame/*?

Comment on lines 17 to 31
# - name: Audit rules
# check_type: changed_files
# condition:
# include: ^polkadot/runtime\/(kusama|polkadot|common)\/.*|^polkadot/primitives/src\/.+\.rs$|^substrate/primitives/.*|^substrate/frame/.*
# exclude: ^polkadot/runtime\/(kusama|polkadot)\/src\/weights\/.+\.rs$|^substrate\/frame\/.+\.md$
# all_distinct:
# - min_approvals: 1
# teams:
# - locks-review
# - min_approvals: 1
# teams:
# - polkadot-review
# - min_approvals: 1
# teams:
# - srlabs
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I change this code to be this then?

Suggested change
# - name: Audit rules
# check_type: changed_files
# condition:
# include: ^polkadot/runtime\/(kusama|polkadot|common)\/.*|^polkadot/primitives/src\/.+\.rs$|^substrate/primitives/.*|^substrate/frame/.*
# exclude: ^polkadot/runtime\/(kusama|polkadot)\/src\/weights\/.+\.rs$|^substrate\/frame\/.+\.md$
# all_distinct:
# - min_approvals: 1
# teams:
# - locks-review
# - min_approvals: 1
# teams:
# - polkadot-review
# - min_approvals: 1
# teams:
# - srlabs
- name: Audit rules
check_type: changed_files
condition:
include: ^polkadot/runtime\/(kusama|polkadot|common)\/.*|^polkadot/primitives/src\/.+\.rs$|^substrate/primitives/.*|^substrate/frame/.*
exclude: ^polkadot/runtime\/(kusama|polkadot)\/src\/weights\/.+\.rs$|^substrate\/frame\/.+\.md$
all_distinct:
- min_approvals: 1
teams:
- locks-review
# - min_approvals: 1
# teams:
# - polkadot-review
# - min_approvals: 1
# teams:
# - srlabs

@paritytech-ci paritytech-ci requested a review from a team August 29, 2023 09:46
@paritytech-ci paritytech-ci requested a review from a team August 29, 2023 09:51
@bkchr
Copy link
Member

bkchr commented Aug 29, 2023

@Bullrich what is blocking this?

After discussing it in the PR this was the agreed solution
@Bullrich
Copy link
Contributor Author

I updated the PR to remove frame and only have the lock-team. Let me know if I'm missing anything

- min_approvals: 1
teams:
- srlabs
include: ^polkadot/runtime\/(kusama|polkadot|common)\/.*|^polkadot/primitives/src\/.+\.rs$|^substrate/primitives/.*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is still wrong... locks-review was about protecting
🔒 🔒 🔒
line of code
🔒 🔒 🔒

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What team should I set here?

So, we probably should only keep locks-review and they can operate on the entire code base for when "locked" code is changed.

We have miss interpreted your message, I thought you referred to using the lock-teams.

Should I simply remove this rule?

Copy link
Contributor

@mordamax mordamax Aug 29, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well it just moved and merged all together from 3 repos + mixed with requirements from paritytech/pr-custom-review#136, there's high chance that it could be done better
Lets revisit these pr-cr settings in scope of monorepo holistically

so in order to implement properly paritytech/pr-custom-review#136 this task, with post-actions like adding a project etc we will need to wait until https://github.com/paritytech/review-bot/milestone/1 is done and we can integrate it here with all new rules

before it's done i think this whole condition from paritytech/pr-custom-review#136 could be removed for now, and keep only the old polkadot one https://github.com/paritytech/polkadot/blob/master/.github/pr-custom-review.yml#L10-L11

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just remove the rules here entirely for now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bkchr you mean all PRCR rules or only Audit?
if all - why?

Copy link
Contributor Author

@Bullrich Bullrich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment just to trigger PRCR again

@Bullrich Bullrich enabled auto-merge (squash) August 29, 2023 15:27
@Bullrich Bullrich merged commit 6bb9ad4 into master Aug 29, 2023
@Bullrich Bullrich deleted the prcr-disable-rule branch August 29, 2023 15:49
bkchr pushed a commit that referenced this pull request Aug 30, 2023
@the-right-joyce has requested to disable the Audit rule until we can fix the problem that it always request reviewers (even if the user belongs to the `prevent-review-request` field.
@ordian ordian mentioned this pull request Sep 6, 2023
Daanvdplas pushed a commit that referenced this pull request Sep 11, 2023
@the-right-joyce has requested to disable the Audit rule until we can fix the problem that it always request reviewers (even if the user belongs to the `prevent-review-request` field.
bkchr pushed a commit that referenced this pull request Apr 10, 2024
* Enable off-chain indexing for Rialto & Millau nodes

* cargo fmt --all

* cargo +nightly fmt --all

* fmt is weird.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants