This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Add release-engineering to CI files' reviewers#5733
Merged
paritytech-processbot[bot] merged 1 commit intomasterfrom Jun 27, 2022
Merged
Add release-engineering to CI files' reviewers#5733paritytech-processbot[bot] merged 1 commit intomasterfrom
paritytech-processbot[bot] merged 1 commit intomasterfrom
Conversation
sergejparity
approved these changes
Jun 27, 2022
alvicsam
approved these changes
Jun 27, 2022
TriplEight
approved these changes
Jun 27, 2022
Contributor
Author
|
bot merge |
Contributor
|
Thanks @joao-paulo-parity ! |
ordian
added a commit
that referenced
this pull request
Jun 28, 2022
* master: zombienet: try to fix parachains upgrade test (#5724) Update dependencies (companion for substrate#11722) (#5731) Update metric name and doc (#5716) Bump reqwest from 0.11.10 to 0.11.11 (#5732) add release-engineering to CI files' reviewers (#5733) Bump parity-scale-codec from 3.1.2 to 3.1.5 (#5720) Add checklist item (#5715) Fix 5560: add support for a new `staking-miner info` command (#5577) Bump `wasmtime` to 0.38.0 and `zstd` to 0.11.2 (companion for substrate#11720) (#5707) pvf: ensure enough stack space (#5712) Bump generic-array from 0.12.3 to 0.12.4 in /bridges/fuzz/storage-proof (#5648) pvf: unignore `terminates_on_timeout` test (#5722) Bump proc-macro2 from 1.0.39 to 1.0.40 (#5719) pass $COMPANION_OVERRIDES to check_dependent_project (#5708) Bump thread_local from 1.1.0 to 1.1.4 in /bridges/fuzz/storage-proof (#5687) Bump quote from 1.0.18 to 1.0.19 (#5700) Rococo: add new pallet-beefy-mmr API (companion for substrate#11406) (#5516) Update metric before bailing out (#5706) Add publish docker staking-miner (#5710)
al3mart
pushed a commit
that referenced
this pull request
Jul 14, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@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. If that's not acceptable for some reason, please suggest alternatives in the comments.