ci: add auto-assign workflow

[jmrplens]

Auto-assigns newly opened issues and PRs to @jmrplens.

Uses gh api with GITHUB_TOKEN, no external dependencies.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's Guide

Adds a GitHub Actions workflow that automatically assigns newly opened issues and pull requests to @jmrplens using the GitHub CLI and the repository’s GITHUB_TOKEN.

Sequence diagram for the new auto-assign GitHub Actions workflow

sequenceDiagram
    actor User
    participant GitHub
    participant AutoAssignWorkflow
    participant GitHubAPI

    User->>GitHub: open issue or pull_request
    GitHub-->>AutoAssignWorkflow: issues.opened / pull_request.opened
    AutoAssignWorkflow->>GitHubAPI: gh api POST /repos/$REPO/issues/$NUMBER/assignees
    GitHubAPI-->>GitHub: assignee jmrplens added
    GitHub-->>User: issue/PR shown with assignee jmrplens

Loading

File-Level Changes

Change	Details	Files
Introduce an auto-assignment GitHub Actions workflow for new issues and pull requests.	Define workflow triggers for opened issues and opened pull requests. Configure a single job that runs on ubuntu-latest with write permissions to issues and pull requests. Set environment variables for GH_TOKEN, repository name, and issue/PR number from the GitHub event context. Use the GitHub CLI to POST to the issues assignees endpoint to assign @jmrplens to the newly opened item.	.github/workflows/auto-assign.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Review limit reached

@jmrplens, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 39c72772-f75f-4b75-bb86-8e735fea6c0f

📥 Commits

Reviewing files that changed from the base of the PR and between 1c1907c and b7706aa.

📒 Files selected for processing (1)

• .github/workflows/auto-assign.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/auto-assign

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Hey - I've left some high level feedback:

• You can simplify and make the NUMBER env more robust by using NUMBER: ${{ github.event.number }}, which is available for both issues and pull_request events instead of relying on github.event.issue.number || github.event.pull_request.number.
• Since the workflow only calls the issues API, you can drop the pull-requests: write job permission to keep the token scope as narrow as possible.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- You can simplify and make the `NUMBER` env more robust by using `NUMBER: ${{ github.event.number }}`, which is available for both `issues` and `pull_request` events instead of relying on `github.event.issue.number || github.event.pull_request.number`.
- Since the workflow only calls the issues API, you can drop the `pull-requests: write` job permission to keep the token scope as narrow as possible.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}