TgWitness / Documentation

Repository / .github/AUTOMATION.md

Repository workflows

TgWitness

TgWitness / Project workflow

GitHub configuration for TgWitness: automation, issue forms and contribution prompts.

Keep this guide named AUTOMATION.md: GitHub gives a .github/README.md priority over the project README at the repository root.

Directory or file Purpose
workflows/ Checks, website, release and wiki workflows
ISSUE_TEMPLATE/ Bug, feature and documentation forms
dependabot.yml Dependency update configuration
pull_request_template.md Contributor review checklist

Workflow definitions describe configured jobs. Their existence is not a passing status or evidence that a release has been published. For current qualification, consult the verification record.

Pull requests run lint, packaging, installed-package smoke and dependency audits on disposable hosted runners. Browser suites run in the private validation environment with synthetic accounts. Pull-request jobs receive no operator credentials and cannot publish a release.

The release workflow also calls the dependency, CodeQL and actual-container audits from the same revision. Source, wheel, portable and container publication all depend on that audit succeeding. The HIGH/CRITICAL image gate includes unfixed findings; a successful functional test cannot override it. A manual Security audit can check a candidate branch before tagging it.