feat: add assign-prs-to-author reusable workflow#4
Open
mattmillerai wants to merge 1 commit into
Open
Conversation
Extracts the housekeeping workflow that assigns every open PR with no assignees to its author into a reusable workflow_call, so consumer repos carry only a thin scheduled caller instead of a copy. Bot-authored PRs are skipped by default (skip-bots input). Uses the caller's GITHUB_TOKEN, so the calling job grants pull-requests: write + issues: write.
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.
What
Adds a third reusable workflow to this repo:
assign-prs-to-author.yml. It assigns every open PR with no assignees to its author, so unassigned PRs get routed back to whoever opened them. Bot-authored PRs (Dependabot, Renovate, app tokens) are skipped by default via theskip-botsinput.Extracted from a copy that currently lives in
Comfy-Org/cloud, following the same thin-caller pattern ascursor-reviewanddetect-unreviewed-merge.Why a reusable workflow
It's generic CI housekeeping with zero repo-specific anything — pure
github-scriptovercontext.repo. Hosting it here means consumer repos carry a small scheduled caller instead of a maintained copy (no drift).Permissions
Uses the caller's
GITHUB_TOKEN(no secrets to pass). The calling job must grantpull-requests: writeandissues: write— assignees are set through the issues API.Caller pattern