Use epiforecasts-workflows app token in render_readme

[sbfnk]

Summary

• Update render_readme.yml to use the epiforecasts-workflows GitHub App token
• This allows PRs created by the workflow to trigger CI checks (R-CMD-check, etc.)
• The default GITHUB_TOKEN doesn't trigger workflows, but the app token does

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow authentication mechanism for internal processes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

GitHub App token generation step introduced using tibdex/github-app-token action. Token replaces default GITHUB_TOKEN in checkout and create pull request steps. Authentication sourced from GitHub App instead of built-in token.

Changes

Cohort / File(s)	Change Summary
GitHub Actions Workflow Token Authentication \.github/workflows/render_readme.yml``	Adds new GitHub App token generation step using tibdex/github-app-token@v2. Replaces default GITHUB_TOKEN with generated token in checkout and create pull request steps.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and clearly summarizes the main change: replacing the default token with the epiforecasts-workflows app token in the render_readme workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 08dd621 and 599c95b.

📒 Files selected for processing (1)

• .github/workflows/render_readme.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: ubuntu-latest (4.4)
• GitHub Check: ubuntu-latest (oldrel-1)
• GitHub Check: macOS-latest (release)
• GitHub Check: ubuntu-latest (release)
• GitHub Check: ubuntu-latest (devel)
• GitHub Check: windows-latest (release)
• GitHub Check: pkgdown

🔇 Additional comments (2)

.github/workflows/render_readme.yml (2)

51-54: LGTM – Checkout step correctly uses the generated token.

The modification to pass token: ${{ steps.generate_token.outputs.token }} to the checkout step is correct. This ensures the generated GitHub App token is used for repository access instead of the default GITHUB_TOKEN.

---

97-109: LGTM – Create Pull Request step correctly uses the generated token.

The modification to pass token: ${{ steps.generate_token.outputs.token }} to the create-pull-request step is correct. This ensures PRs created by the workflow will use the GitHub App's authentication, allowing them to trigger CI checks (R-CMD-check and others) as intended by the PR objectives.