YTDescGen is feature-complete; from 1.6.0 on it is maintained, not extended. Still accepted: scheduled dependency updates; fixes for high or critical CVEs and serious runtime issues; major language / runtime / framework upgrades; bug, UI/UX and accessibility fixes, and options added to or removed from the app's lists when people really need them; translation fixes; Cloudflare / Worker changes the platform forces and website incidents. - README: status, CI, Qodana and SonarCloud badges; a Project status section; Contributing and the Roadmap row follow it. - CONTRIBUTING: a Maintenance mode section, Option requests, issue and pull request rules, What We Want / Don't Want. - SECURITY, MAINTAINERS, CLAUDE.md: the policy where each one needs it. - ROADMAP: status block, a Maintenance mode section, Phase 5 and the backlog frozen. FEATURES: the extension points are frozen. - Issue forms: Feature request removed; Option request and Translation or wording fix added; Bug report and Accessibility barrier now carry the `needs-triage` label (`triage` never existed). config.yml points feature ideas at Discussions → Ideas. The PR template gains a Scope checklist. - maintenance-triage.yml closes, with a bilingual comment and the `out-of-scope` label, feature issues and `feat:` pull requests from outside contributors (scopes options, a11y and i18n stay open) and anything labelled `out-of-scope`. pull_request_target without checkout; listed under zizmor's dangerous-triggers ignore with the reason. Labels created on the repository: out-of-scope, needs-triage, i18n, option-request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
1.3 KiB
YAML
27 lines
1.3 KiB
YAML
# zizmor (workflow security linter) configuration — see security.yml.
|
|
rules:
|
|
unpinned-uses:
|
|
config:
|
|
policies:
|
|
# The shared notification / announcement workflows live in the
|
|
# maintainer's own `poli0981/.github` repository and are deliberately
|
|
# tracked at `main`, so a fix there reaches every repo at once.
|
|
"poli0981/*": any
|
|
# Everything else must be pinned to a full commit SHA.
|
|
"*": hash-pin
|
|
dangerous-triggers:
|
|
ignore:
|
|
# Both run on `workflow_run` so a failure (or a release build) anywhere
|
|
# can be reported to Discord. Neither checks out the triggering run's
|
|
# code nor downloads its artifacts: the shared workflows only read run
|
|
# metadata, and pass every untrusted field (branch, commit message,
|
|
# actor) to the notifier script through `env:`, never by interpolation.
|
|
- notify-ci-failure.yml
|
|
- notify-release-pipeline.yml
|
|
# Runs on `pull_request_target` so it can label, comment on and close
|
|
# an out-of-scope pull request from a fork (maintenance mode). It never
|
|
# checks out the pull request, runs none of its code, and reads the
|
|
# title from the event payload inside the script — nothing from the
|
|
# pull request is interpolated into the workflow.
|
|
- maintenance-triage.yml
|