Skip to content

[dev]: project-neutral organization bug form and working membership links #769

Closed

Description

@ss-o

Your feedback for the existing codebase

The organization bug form .github/ISSUE_TEMPLATE/01_bug_report.yml is written for Zi: its Environment example reads $ZI[BIN_DIR], and Additional information asks for zi analytics. It is the live bug form for every repository without its own .github/ISSUE_TEMPLATE/ (zpmod, H-S-MW, the annexes and most plugins), and zsh-lint and wiki carry vendored copies of it. Non-Zi reports therefore miss the project's version, the loading method and an isolated reproduction; zpmod #31 needed follow-up comments for the Zsh version, commit and build method. The form also requires a code snippet and additional information that many bugs do not have, and takes the environment as a one-line input.

The membership form 05_membership.yml links to two pages that return 404: governance/README.md and https://github.com/z-shell/.github/main/governance/organization/CODE-OF-CONDUCT.md (no /blob/, and the file has moved).

Acceptance criteria:

  • The organization bug form asks, project-neutrally, for the affected version, branch or commit; the environment (Zsh version, OS, how the project is loaded) as a multi-line field; a minimal reproduction from zsh -f or a clean HOME; the actual and expected behavior; and optional additional information. Its labels, assignee, title and policy checkboxes are unchanged.
  • The membership form links resolve to .github/GOVERNANCE.md and .github/CODE_OF_CONDUCT.md.
  • The template exception reasons in knowledge/domains/governance/data/template-exceptions.yml that compare against the organization bug form stay accurate.
  • The vendored copies in z-shell/zi (05_membership.yml), z-shell/zsh-lint and z-shell/wiki (01_bug_report.yml, 05_membership.yml) are synchronized in follow-up pull requests so the community-health audit reports no drift.

Contact Details

Not applicable: filed by a maintainer.

Activity

  1. self-assigned this
    on Oct 8, 2026
  2. added
    type:maintenanceNon-feature maintenance, cleanup, or org work.
    area:metaOrganization-wide policy, templates, or meta-repo work.
    on Oct 8, 2026
  3. ss-o commented on Oct 8, 2026

    @ss-o
    MemberAuthor

    Project 28 triage. Values set on this new issue:

    • Item Type: Chore. A change to organization issue forms and their records.
    • Impact: Medium. The bug form is the intake for every repository without its own forms.
    • Effort: S. Two form files and two exception reasons here, then three copy-only sync pull requests.
    • Priority: P2 - Medium. It improves bug intake but blocks no release.
    • Workstream: Administrative. Organization process.
    • Status: In Progress. The change is ready for a pull request.
  4. ss-o commented on Oct 9, 2026

    @ss-o
    MemberAuthor

    Progress on the acceptance criteria:

    Next action: close this issue once the zi promotion that contains 12889b7 is merged.

  5. ss-o commented on Oct 9, 2026

    @ss-o
    MemberAuthor

    All acceptance criteria are met. #770 made the organization bug form project-neutral and fixed the membership form links. z-shell/zi#627, z-shell/zsh-lint#603 and z-shell/wiki#941 synchronized the vendored copies, and the zi change is on zi main. #777 refreshed the zi exception pins after the zi cutover. The Community Health Audit on main at 5a36c91 reports no drift in any repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:metaOrganization-wide policy, templates, or meta-repo work.type:maintenanceNon-feature maintenance, cleanup, or org work.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions