Connect with a GitHub token instead of the app
The normal way to connect is to install the GitHub App. If that is not possible, for example an organisation owner has to approve apps and you would rather not ask, you can connect with a GitHub access token instead. It is an advanced option on every plan.
What changes
- Your name appears as the author. Merges and revert pull requests are made by your own GitHub account, not by the app.
- No heads-up for merges made outside the app, because we do not get GitHub events in this mode.
- The token expires. We email you 14 days before, 3 days before and on the day. After that, scheduled merges fail until you add a new token.
- We store the token, encrypted. It is never shown again. Anyone who has it can write to the repos you chose, so keep it small.
Create the token
- On GitHub open Settings, Developer settings, Fine-grained tokens, Generate new token.
- Choose Only select repositories and pick the repos you want to schedule. For an organisation, set the resource owner to it. An owner may need to approve the token.
- Set Contents and Pull requests to Read and write. Set Actions, Commit statuses and Checks to Read.
- Pick the shortest expiry you are comfortable with. Copy the token.
Connect it
- Open Settings, GitHub, and choose Advanced: connect with a GitHub token.
- Tick that you understand the four points, paste the token and press Connect with token.
- We check it with GitHub. It must belong to the account you are signed in with and be able to push to at least one repo.
- Add your repos as usual.
Replace or remove it
- Before it expires, press Replace token and paste a new one. Your repos keep working.
- To stop, remove the repos that use it, then press Remove. The stored token is deleted.
- If you think the token leaked, revoke it on GitHub first, then remove it here.
More guides: Use Merge Scheduler with Vercel, Netlify or another deploy tool · Get email, Slack and Discord alerts for every release