kjh2064/QuantEngineByItz
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs/tools: Gitea token home & PR harness 검증 도구 개선
Quant Engine CI/CD Pipeline / validate-core (push) Failing after 13s
Details
Quant Engine CI/CD Pipeline / validate-ui-and-storage (push) Has been skipped
Details
Deploy to Production / Build & Deploy to Production (push) Failing after 2m27s
Details

Browse Source 
- docs/GITEA_TOKEN_HOME.md: 토큰 홈 설정 문서 업데이트
- docs/GITEA_TOKEN_HOME_RUNBOOK.md: 런북 보완
- docs/GITEA_VARIABLES_FAILURE_ANALYSIS.md: 실패 분석 문서 수정
- docs/GITEA_VARIABLES_RUNBOOK.md: 변수 런북 수정
- tools/validate_gitea_pr_harness_v1.py: PR 하네스 검증 스크립트 개선
- tools/validate_gitea_token_home_v1.py: 토큰 홈 검증 스크립트 개선
This commit is contained in:
김재현
2026-07-06 17:15:21 +09:00
parent 324313d8f3
commit a5493142f9
6 changed files with 18 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/GITEA_VARIABLES_FAILURE_ANALYSIS.md
+1 -1
View File
@@ -15,7 +15,7 @@ Likely causes:
Empirical note:
- A direct API dispatch probe to the workflow endpoint returned `401 Unauthorized` in this workspace, which means API-triggered execution still needs a valid repository token.
- With `GITEA_TOKEN_HOME`, dispatch succeeds and creates a queued run, so the remaining bottleneck can be runner capacity rather than API auth.
- With `GITEA_TOKEN_TAXBAIK`, dispatch succeeds and creates a queued run, so the remaining bottleneck can be runner capacity rather than API auth.
Observed root cause for `run 161`: