Skip to content

upgraded review bot to v2.1.0#1908

Merged
Bullrich merged 2 commits intomasterfrom
bullrich/review-bot/upgrade
Oct 18, 2023
Merged

upgraded review bot to v2.1.0#1908
Bullrich merged 2 commits intomasterfrom
bullrich/review-bot/upgrade

Conversation

@Bullrich
Copy link
Copy Markdown
Contributor

Upgraded to version 2.1.0 which has paritytech/review-bot#94, a change in the logic of the action to overcome some problems with permissions coming from PRs from forks

For this, we needed to divide the actions into two files:

  • A first action that triggers on PRs and reviews and uploads the PR number.
  • A second action which is triggered under the completion of the first one and runs as the action normally runs (but won't have any problems regarding permissions because it is triggered from the master branch)

Upgraded to version 2.1.0 which has paritytech/review-bot#94, a change in the logic of the action to overcome some problems with permissions coming from PRs from forks

For this, we needed to divide the actions into two files:
- A first action that triggers on PRs and reviews and uploads the PR number.
- A second action which is triggered under the completion of the first one and runs as the action normally runs (but won't have any problems regarding permissions because it is triggered from the master branch)
@Bullrich Bullrich added the R0-no-crate-publish-required The change does not require any crates to be re-published. label Oct 17, 2023
@Bullrich Bullrich self-assigned this Oct 17, 2023
@Bullrich Bullrich requested review from a team as code owners October 17, 2023 11:20
@Bullrich
Copy link
Copy Markdown
Contributor Author

@pavelsupr we can enable environment secrets again with this new implementation.

@paritytech-ci paritytech-ci requested a review from a team October 18, 2023 11:03
@Bullrich Bullrich enabled auto-merge (squash) October 18, 2023 11:18
@Bullrich Bullrich merged commit 1cf7d3a into master Oct 18, 2023
@Bullrich Bullrich deleted the bullrich/review-bot/upgrade branch October 18, 2023 12:04
ordian added a commit that referenced this pull request Oct 20, 2023
* tsv-disabling: (39 commits)
  Handling of disabled validators in backing subsystem (#1259)
  Switch trie cache random seed (#1935)
  Expose prometheus metrics for minimal-relay-chain node in collators (#1942)
  Do not force collators to update after enabling async backing (#1920)
  Pin PRDoc image to v0.0.5 until we are ready for v0.0.6 (#1947)
  [prdoc] Start BEEFY gadget by default for Polkadot nodes (#1945)
  Update bridges subtree  (#1944)
  bump zombienet version (#1931)
  [FRAME] Message Queue use proper overweight limit (#1873)
  Cumulus: Allow aura to use initialized collation request receiver (#1911)
  Use prebuilt try-runtime binary in CI (#1898)
  Update kusama/polkadot bootnodes (#1895)
  Introduce XcmFeesToAccount fee manager (#1234)
  upgraded review bot to v2.1.0 (#1908)
  Trading trait and deal with metadata in Mutate trait for nonfungibles_v2 (#1561)
  Add Runtime Missing Crate Descriptions (#1909)
  Switch to the release env (#1910)
  Bump paritytech/review-bot from 2.0.1 to 2.1.0 (#1924)
  Bump actions/checkout from 4.1.0 to 4.1.1 (#1925)
  Start BEEFY client by default for Polkadot nodes (#1913)
  ...
tdimitrov pushed a commit that referenced this pull request Oct 23, 2023
Upgraded to version 2.1.0 which has paritytech/review-bot#94, a change
in the logic of the action to overcome some problems with permissions
coming from PRs from forks

For this, we needed to divide the actions into two files:
- A first action that triggers on PRs and reviews and uploads the PR
number.
- A second action which is triggered under the completion of the first
one and runs as the action normally runs (but won't have any problems
regarding permissions because it is triggered from the master branch)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

R0-no-crate-publish-required The change does not require any crates to be re-published.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants