The actions/gitea-issue-create@v1 action does not exist on GitHub, causing the docs-drift workflow to fail every run with authentication required: Repository not found
Replaced with a direct curl call to the Gitea REST API (POST /api/v1/repos/{repo}/issues), which works natively on the self-hosted instance
Corrected the issue label from documentation to Kind/Documentation
Manual Verification
Merge this PR and push a change to README.md on mainwithout touching docs/fish-config.md — confirm the workflow runs to completion and opens a new issue with the label Kind/Documentation
Push a change to README.mdwith a matching update to docs/fish-config.md in the same commit — confirm the workflow runs but does not open an issue
Confirm the opened issue body contains the correct commit SHA and branch name
Confirm the GITEA_TOKEN secret is present in the repo settings (Settings → Actions → Secrets)
## Summary
- The `actions/gitea-issue-create@v1` action does not exist on GitHub, causing the docs-drift workflow to fail every run with `authentication required: Repository not found`
- Replaced with a direct `curl` call to the Gitea REST API (`POST /api/v1/repos/{repo}/issues`), which works natively on the self-hosted instance
- Corrected the issue label from `documentation` to `Kind/Documentation`
## Manual Verification
- [x] Merge this PR and push a change to `README.md` on `main` **without** touching `docs/fish-config.md` — confirm the workflow runs to completion and opens a new issue with the label `Kind/Documentation`
- [x] Push a change to `README.md` **with** a matching update to `docs/fish-config.md` in the same commit — confirm the workflow runs but does **not** open an issue
- [x] Confirm the opened issue body contains the correct commit SHA and branch name
- [x] Confirm the `GITEA_TOKEN` secret is present in the repo settings (Settings → Actions → Secrets)
The `actions/gitea-issue-create@v1` action does not exist on GitHub,
causing the docs-drift workflow to fail at clone time. Replace it with
a direct call to the Gitea REST API using curl. Also corrects the label
from `documentation` to `Kind/Documentation`.
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.
Summary
actions/gitea-issue-create@v1action does not exist on GitHub, causing the docs-drift workflow to fail every run withauthentication required: Repository not foundcurlcall to the Gitea REST API (POST /api/v1/repos/{repo}/issues), which works natively on the self-hosted instancedocumentationtoKind/DocumentationManual Verification
README.mdonmainwithout touchingdocs/fish-config.md— confirm the workflow runs to completion and opens a new issue with the labelKind/DocumentationREADME.mdwith a matching update todocs/fish-config.mdin the same commit — confirm the workflow runs but does not open an issueGITEA_TOKENsecret is present in the repo settings (Settings → Actions → Secrets)