triage.yml labels a feature request enhancement and out-of-scope, answers in English and Vietnamese with CONTRIBUTING linked, and closes it as not planned — on unmistakable signals only: a title that says it is one, a feat: pull request, or the enhancement label going on. Maintainers, bots and policy-exception are never closed. The rules live in .github/scripts/triage.cjs with node --test cases (run by npm licences); pull_request_target checks out only the base branch's scripts; workflow_dispatch is a dry run. notify.yml hears about it. Templates: a Wording or translation form (i18n), a contact link saying features are not taken, a maintenance note on the bug form, and the kinds of change a pull request can be. eslint.config.js lints the CommonJS helper as Node, outside the type-aware program. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
15 lines
995 B
YAML
15 lines
995 B
YAML
# RELEASE-CI.md §5: blank issues disabled so every report carries the fields the triage flow and
|
|
# the in-app "Report bug" deep link depend on (ERROR-CATALOG §4).
|
|
blank_issues_enabled: false
|
|
|
|
contact_links:
|
|
- name: Feature request — not accepted during maintenance
|
|
url: https://github.com/poli0981org/pipdock/blob/main/CONTRIBUTING.md#scope-in-maintenance-mode
|
|
about: Since 1.6.0 PipDock takes fixes, not features. An issue or pull request asking for one is closed automatically; this explains what is accepted, and where to argue that something is truly necessary.
|
|
- name: Question or idea
|
|
url: https://github.com/poli0981org/pipdock/discussions
|
|
about: Ask about usage or share a workflow. Ideas are welcome to discuss, but during maintenance they are not on a roadmap.
|
|
- name: Security vulnerability
|
|
url: https://github.com/poli0981org/pipdock/security/advisories/new
|
|
about: Report privately via GitHub Security Advisories. Please do not open a public issue.
|