Labyricorn/thinkloom-openai-hackathon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document Labyricorn refresh dispatch

Browse Source
This commit is contained in:
Labyricorn
2026-08-11 23:27:27 -07:00
parent a4ad2ad10a
commit e3b9a90181
2 changed files with 17 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.labyricorn/AGENTS.md
+13 -3
View File
@@ -50,9 +50,19 @@ those directories.
command example.
- Do not claim that content is public merely because a push succeeded. Report
push status and synchronization/publication status separately.
- When an authenticated refresh mechanism is implemented and documented, use
only its approved wrapper command and request at most one refresh for a pushed
commit. Until then, do not invent or bypass a trigger mechanism.
- After an explicitly authorized push that changes `.labyricorn/`, request at
most one refresh through the site repository's documented Gitea
`workflow_dispatch` endpoint. Use `POST` with `{"ref":"main"}` and an
`Authorization: token ...` header supplied from the approved
`LABYRICORN_REFRESH_TOKEN` environment or credential store.
- The endpoint is
`https://git.labyricorn.com/api/v1/repos/Labyricorn/labyricorn-site/actions/workflows/deploy.yml/dispatches`.
Never place its credential in the URL, this repository, an `AGENTS.md` file,
output, or logs. If the credential is unavailable, do not improvise: the
scheduled synchronization runs every 30 minutes.
- A successful dispatch only queues synchronization. Verify the Action result
and the imported revision on the public project page before reporting that
publication completed.
## Validation and handoff