Create an automation GitHub App for actions

adminリポジトリの request-an-access-token.md と、リンクされている GitHub App 認証ドキュメントから始めます。提案されている権限とリポジトリへのアクセス許可プロセスを、release-please のワークフロー例を含めて確認します。組織に制限された GitHub App が指定された権限で存在し、リポジトリへのアクセスに管理者へのリクエストが必要で、登録プロセスが文書化されていれば完了です。

To automate common workflows like release-please and dependency updaters, a personal access token or a github app installation token is required to trigger subsequent GitHub Action workflows.

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow#triggering-a-workflow-from-a-workflow

However, GitHub does not allow creating PAT via API. This makes it awkward to automate token creation.

I propose creating a GitHub App in the @nodejs organization with the following permissions:

• contents: write and pull-requests: write (permissions to create tags and pull requests, requested by release-please and for dependency updaters),
• This GitHub App needs explicit granting to specific repositories, via explicit requests in the admin repo,
• Only allow this GitHub App to be installed on the @nodejs account.

With this new GitHub app, new github action workflows can follow https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow to automate the token authentication. (example)

Granting the app to a repository still needs registering in this admin repo for awareness.

This is only for common workflows. Requesting permissions for customized workflows that need additional permissions should still follow the steps in https://github.com/nodejs/admin/blob/main/request-an-access-token.md.