ci: Use GitHub App token for CI workflow

[Aaron ("AJ") Steers (aaronsteers)]

Replace the personal access token with a GitHub App token for improved security and explicitly define the repository owner in the CI configuration.

Summary by CodeRabbit

• Chores
  • Improved workflow authentication by switching from a static personal access token to a dynamically generated GitHub App token for posting status updates.
  • Updated workflow job names for clarity.

[coderabbitai]

Warning

Rate limit exceeded

Aaron ("AJ") Steers (@aaronsteers) has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 52 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 392a61b and d64b126.

📒 Files selected for processing (1)

• .github/workflows/test-pr-command.yml (4 hunks)

📝 Walkthrough

Walkthrough

The workflow for handling pull request test commands was updated to authenticate using a GitHub App token instead of a static personal access token. The job names and outputs were adjusted accordingly, and the dynamic token is now used for posting check statuses in place of the previous static secret.

Changes

File(s)	Change Summary
.github/workflows/test-pr-command.yml	Renamed job, added GitHub App authentication step, exposed token as output, and switched check status token usage

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant GitHub App

    Developer->>GitHub Actions: Open PR / trigger workflow
    GitHub Actions->>GitHub App: Authenticate (create-github-app-token)
    GitHub App-->>GitHub Actions: Return gh-app-token
    GitHub Actions->>GitHub Actions: Run workflow steps (use gh-app-token)
    GitHub Actions->>GitHub: Post check status (in_progress/completed) using gh-app-token

Loading

Possibly related PRs

• ci: add check statuses to PRs from slash command execution #683: Added the posting of check statuses in the same workflow, which is now directly affected by the authentication change in this PR. Wdyt about reviewing these changes together for consistency?

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Pull Request Overview

This PR replaces the personal access token used in the CI workflow with a GitHub App token to improve security and explicitly defines the repository owner. Key changes include adding a new authentication step using the GitHub App token, updating job outputs to include the new token, and replacing usages of the old token with the new one.