release-verify: expand YAML anchors in gost config, add tea command rules
ci-deploy / build-deploy-test (push) Successful in 1m17s

This commit is contained in:
2026-04-28 20:48:15 +03:00
parent 213f76a7b4
commit 1e9184dc37
2 changed files with 18 additions and 2 deletions
+12 -2
View File
@@ -27,7 +27,7 @@ chains:
bypasses: bypasses:
- name: tim-whitelist - name: tim-whitelist
whitelist: true whitelist: true
matchers: &tim_matchers matchers:
- ".webzavod.ru" - ".webzavod.ru"
- ".devwebzavod.ru" - ".devwebzavod.ru"
- ".aeroflot.ru" - ".aeroflot.ru"
@@ -41,4 +41,14 @@ bypasses:
- name: tim-blacklist - name: tim-blacklist
whitelist: false whitelist: false
matchers: *tim_matchers matchers:
- ".webzavod.ru"
- ".devwebzavod.ru"
- ".aeroflot.ru"
- "webzavod.ru"
- "devwebzavod.ru"
- "aeroflot.ru"
- "46.235.186.67"
- "195.209.66.54"
- "195.209.82.146"
- "46.235.189.158"
+6
View File
@@ -174,3 +174,9 @@ The following are contractual hard constraints for the remote frontend component
- Never add `Co-Authored-By` lines to commit messages. - Never add `Co-Authored-By` lines to commit messages.
- Commit messages in English, concise, focused on "why" not "what". - Commit messages in English, concise, focused on "why" not "what".
- Commit autonomously when changes are complete and stable — no need to ask for permission. Group related edits into logical commits. Still ask before pushing, force-pushing, or any destructive git operation. - Commit autonomously when changes are complete and stable — no need to ask for permission. Group related edits into logical commits. Still ask before pushing, force-pushing, or any destructive git operation.
## Gitea / Tea Command Rules
- Use `tea` command to check Gitea workflow runs: `tea run list --limit 5` to see last 5 runs
- Use `tea run view <run-id>` to inspect a specific run
- Use `tea run rerun <run-id>` to re-run a failed workflow