Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Add release-engineering to CI files' reviewers #1413

Merged
merged 1 commit into from
Jun 30, 2022

Conversation

joao-paulo-parity
Copy link
Contributor

Similar to what was done for paritytech/polkadot#5733.

@paritytech/release-engineering frequently edits the files reviewed by CI, for instance

The ownership of files in those directories either overlaps with @paritytech/ci or are instead owned by @paritytech/release-engineering, therefore it makes sense to more accurately represent their ownership through pr-custom-review's rules.

After discussion on Matrix, @TriplEight mentioned that it would be fine for @paritytech/release-engineering to be included in the "CI files" rule.

@joao-paulo-parity joao-paulo-parity added A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low 📌 labels Jun 27, 2022
@joao-paulo-parity joao-paulo-parity requested review from a team and chevdor as code owners June 27, 2022 12:38
@paritytech-ci paritytech-ci requested a review from a team June 27, 2022 12:47
@joao-paulo-parity
Copy link
Contributor Author

bot merge

@paritytech-processbot paritytech-processbot bot merged commit 6962b1b into master Jun 30, 2022
@paritytech-processbot paritytech-processbot bot deleted the jp/prcr-rules branch June 30, 2022 08:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants