ci: skip self-assignment

[jmrplens]

El workflow ahora no asigna si el autor es @jmrplens.

Summary by Sourcery

CI:

• Add a conditional to the auto-assign workflow so it only runs when the author is not jmrplens.

[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 (collapsed on small PRs)

Reviewer's Guide

The workflow for auto-assigning issues/PRs to jmrplens is updated to skip assignment when jmrplens is the author, and the gh api call is reformatted for readability.

Flow diagram for updated auto-assign CI workflow condition

flowchart TD
  A[GitHub event: issue or pull_request] --> B[Check event_name]
  B --> C[Author login == jmrplens]
  C -- Yes --> D[Skip auto-assign job]
  C -- No --> E[Run auto-assign job]
  E --> F[Call gh_api to assign jmrplens]

Loading

File-Level Changes

Change	Details	Files
Add conditional execution so the auto-assign job does not run when the author is jmrplens.	Introduce an if expression at the job level checking event type and author login. Ensure both issues and pull_request events are covered with separate conditions. Prevent self-assignment by excluding events authored by user login 'jmrplens'.	.github/workflows/auto-assign.yml
Improve formatting of the gh api command used to assign issues/PRs.	Rewrite the single-line gh api command into a multi-line, backslash-continued shell command. Preserve all existing flags and endpoint but spread them across lines for readability.	.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, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review 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 refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d4fba465-837c-48e6-9fc8-db4b852c8251

📥 Commits

Reviewing files that changed from the base of the PR and between 638bb53 and 4405113.

📒 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-skip-self

---

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:

• The updated gh api command no longer includes the -f assignees[]=jmrplens flag, so the workflow will stop assigning the issue/PR to jmrplens; consider restoring that argument after reformatting the command.
• To make the self-assignment check more robust, consider using github.actor instead of the event payload user login, which better reflects the user who triggered the workflow.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The updated `gh api` command no longer includes the `-f assignees[]=jmrplens` flag, so the workflow will stop assigning the issue/PR to `jmrplens`; consider restoring that argument after reformatting the command.
- To make the self-assignment check more robust, consider using `github.actor` instead of the event payload user login, which better reflects the user who triggered the workflow.

---

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.}