Migrate from tibdex/github-app-token to actions/create-github-app-token

[rtibblesbot]

Phase 1: Update all 9 workflow files

Phase 1: Update All 9 Workflow Files

Summary

Apply a mechanical find-and-replace across all 9 workflow files. Each file has the same 3-line block to update.

Changes per file

For each of the 9 files listed below, replace:

- uses: tibdex/github-app-token@v2
  id: generate-token
  with:
    app_id: ${{ secrets.LE_BOT_APP_ID }}
    private_key: ${{ secrets.LE_BOT_PRIVATE_KEY }}

With:

- uses: actions/create-github-app-token@v2
  id: generate-token
  with:
    app-id: ${{ secrets.LE_BOT_APP_ID }}
    private-key: ${{ secrets.LE_BOT_PRIVATE_KEY }}

Affected files

1. .github/workflows/community-contribution-label.yml
2. .github/workflows/contributor-issue-comment.yml
3. .github/workflows/contributor-pr-reply.yml
4. .github/workflows/holiday-message.yml
5. .github/workflows/is-contributor.yml
6. .github/workflows/manage-issue-header.yml
7. .github/workflows/pr-statistics.yml
8. .github/workflows/unassign-inactive-issues.yaml
9. .github/workflows/update-pr-spreadsheet.yml

Notes

• The id: generate-token and output reference ${{ steps.generate-token.outputs.token }} remain unchanged since the output key token is the same in both actions.
• Only 3 lines change per file: uses:, app_id: → app-id:, private_key: → private-key:.

Phase 2: Verify no remaining tibdex references and lint

Phase 2: Verify Migration and Lint

Steps

1. Grep for tibdex across the entire repo to confirm zero remaining references.
2. Run pre-commit run --all-files to ensure:
   • check-yaml passes (YAML is valid)
   • actionlint passes (workflow syntax is correct)
   • yamlfmt doesn't reformat (our edits match the formatter's expectations)
3. Fix any lint issues if the formatter adjusts indentation or spacing.
4. Commit with a clear message referencing issue Migrate from tibdex/github-app-token to actions/create-github-app-token #48.

Summary

Migrate all 9 GitHub Actions workflows from tibdex/github-app-token@v2 to the official actions/create-github-app-token@v2 action. This addresses the deprecation of the third-party action in favor of the GitHub-maintained alternative.

Changes per workflow file:

• uses: tibdex/github-app-token@v2 → uses: actions/create-github-app-token@v2
• app_id: → app-id: (hyphenated input name)
• private_key: → private-key: (hyphenated input name)

The output key token and step ID generate-token remain unchanged, so no downstream references need updating.

Also includes pre-commit auto-fixes for trailing whitespace, missing end-of-file newlines in issue templates, and yamlfmt formatting.

References

• Closes Migrate from tibdex/github-app-token to actions/create-github-app-token #48
• actions/create-github-app-token — official replacement action

Reviewer guidance

• The core change is mechanical: 3 lines updated identically in each of the 9 workflow files. Review one file and spot-check the rest.
• The dependabot.yml and issue template changes are whitespace-only fixes from pre-commit hooks (trailing whitespace, missing EOF newlines, yamlfmt formatting).
• To verify: grep for tibdex across the repo — should return zero matches in tracked files.
• Functional testing requires the LE_BOT_APP_ID and LE_BOT_PRIVATE_KEY secrets, so workflows can only be fully validated by triggering them in the org environment.

Test evidence

Verification steps performed

1. No remaining tibdex references: grep -r tibdex returns zero matches in tracked files.

2. pre-commit checks pass:

trim trailing whitespace.................................................Passed
check yaml...............................................................Passed
check for added large files..............................................Passed
debug statements (python)................................................Passed
fix end of files.........................................................Passed
yamlfmt..................................................................Passed
Lint GitHub Actions workflow files.......................................Passed

3. actionlint validation: All 9 workflow files pass actionlint (run as part of pre-commit).

4. Affected workflow files (all 9 updated):

   • community-contribution-label.yml
   • contributor-issue-comment.yml
   • contributor-pr-reply.yml
   • holiday-message.yml
   • is-contributor.yml
   • manage-issue-header.yml
   • pr-statistics.yml
   • unassign-inactive-issues.yaml
   • update-pr-spreadsheet.yml

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

• Ran pre-flight CI checks (lint, format, tests) and verified all pass
• Rebased onto the target branch and resolved any conflicts
• Reorganized commit history into clean, logical commits
• Audited the diff to ensure only issue-relevant files are changed
• Built PR body from the repository's PR template with evidence blocks

Closes #48

[learning-equality-bot]

Season's greetings! 👋

We'd like to thank everyone for another year of fruitful collaborations, engaging discussions, and for the continued support of our work. Learning Equality will be on holidays from December 22 to January 5. We look forward to much more in the new year and wish you a very happy holiday season!

Are you preparing for Google Summer of Code? See our GSoC guidelines.

[learning-equality-bot]

👋 Thanks for contributing!

We will assign a reviewer within the next two weeks. In the meantime, please ensure that:

• You ran pre-commit locally
• All issue requirements are satisfied
• The contribution is aligned with our Contributing guidelines. Pay extra attention to Using generative AI. Pull requests that don't follow the guidelines will be closed.

We'll be in touch! 😊