syntaqxA repository's settings, security and observability pages fail one part at a time, and never say something false because a read failed. Settings: Add team ("No other team to add" was what a failure said); the default branch's rules (a failure said no rules held for it and anyone could push); General's Branches, Artifacts, Features and Commits sections show Unavailable instead of forms that could save over values never read (Branches and retention used to fail the page); Rules' "what holds for a branch" and Insights. Security: the overview's code scanning, policy and advisories rows say Unavailable instead of guessing "None yet" or "Needs setup", and Open alerts says when code scanning is not in its counts; custom patterns (a failure showed the sales prompt); a secret's validity check (a failure said checks were off); whether reporting is on is unknown, not off. Observability: the overview, open errors ("No open errors in this period"), the g1t.page switch, retention, exports, usage, tokens and a metric's chart each say so in place; the lists use Unavailable. Kept quiet on purpose: the creator's name, the deployments-on preview warning, checks seen for offering CI and in a ruleset's suggestions, a security row's fix status, filter facets (a filter in the address still applies). Checked: apps/web tsc -b; npm test (987, 1 skipped).8b53af5History
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml