Links howto/create-access-tokens.md from the README's .env (credentials) section, next to the "Token permissions" reference. It is the place where a reader who needs a token looks first.
Why a second pull request
PR 63 added the guide and linked it from "Token permissions". This link was committed and pushed to the branch of PR 63 after that PR had been merged, so it never reached main. This pull request carries that one commit, applied on top of the current main.
Issues
None. This is documentation outside the milestones, so there is no issue to close.
## What
Links `howto/create-access-tokens.md` from the README's `.env` (credentials) section, next to the "Token permissions" reference. It is the place where a reader who needs a token looks first.
## Why a second pull request
PR 63 added the guide and linked it from "Token permissions". This link was committed and pushed to the branch of PR 63 after that PR had been merged, so it never reached `main`. This pull request carries that one commit, applied on top of the current `main`.
## Issues
None. This is documentation outside the milestones, so there is no issue to close.
The `.env` (credentials) section now points to howto/create-access-tokens.md
next to the Token permissions reference, so a reader who needs a token finds
the step-by-step guide where the credentials are described.
Tirsvad
merged commit b1c1fbf178 into main2026-10-08 07:06:46 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Links
howto/create-access-tokens.mdfrom the README's.env(credentials) section, next to the "Token permissions" reference. It is the place where a reader who needs a token looks first.Why a second pull request
PR 63 added the guide and linked it from "Token permissions". This link was committed and pushed to the branch of PR 63 after that PR had been merged, so it never reached
main. This pull request carries that one commit, applied on top of the currentmain.Issues
None. This is documentation outside the milestones, so there is no issue to close.