TirSystem-BashScript/repo-foundry
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Fix the Quality status context in the release workflow
Quality checks / quality-checks (pull_request) Successful in 30s
Details
Quality / quality (pull_request) Successful in 30s
Details

Browse Source 
The real context of the Quality run on a push is
"Quality / quality (push)", not the nested job name. Also store the file
with LF line endings, as .editorconfig requires.
This commit is contained in:
Tirsvad
2026-10-12 17:29:29 +08:00
parent 88eac33602
commit cc03cf420d
1 changed files with 56 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/release.yml
+1 -1
View File
@@ -52,5 +52,5 @@ jobs:
# The status context of the Quality run on the commit. Check the exact # The status context of the Quality run on the commit. Check the exact
# text on a pull request and correct it here if the dry run says the # text on a pull request and correct it here if the dry run says the
# run was not found. # run was not found.
VALIDATION_CONTEXT: "Quality / quality / quality-checks (push)" VALIDATION_CONTEXT: "Quality / quality (push)"
run: python3 shared-scripts/tools/release.py run: python3 shared-scripts/tools/release.py