Repository navigation
Conversation
Review requests are posted to the #rfr Slack channel by hand, so some are late or missed. A workflow in treeverse/dev posts them; this one asks it to post or update the PR's message, passing the repository and PR number. PRs from forks, drafts and bot PRs are skipped.
This branch has not been deployed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Change Description
Background
Review requests are posted to the team's Slack review channel by hand, so some are late or missed. A workflow in a Treeverse-internal repository posts them automatically.
New Feature
Adds a small workflow that asks that one to post this repository's PRs: one message per PR that is ready for review, mentioning the requested reviewers, and kept current as reviewers change. It passes only the repository name and PR number. PRs from forks, drafts and bot PRs are skipped, and the job is skipped until its credential is configured.
Testing Details
The command that starts the internal workflow was run by hand and started it. Not tested: this workflow running end to end, since its credential does not exist yet.
Breaking Change?
No.
🤖 Generated with Claude Code