Skip to content

Create or verify the zed-pkg-project GitHub Projects v2 board #13

Closed

Description

@ORESoftware

Context

The canonical Linear portfolio project is github.com/zed-pkg (project UUID 9107ce62-1112-43ff-89bc-f442613c4156). The intended GitHub Projects v2 title is zed-pkg-project.

During the 2026-08-05 verification, the connected repository/Actions API did not expose Projects v2 GraphQL mutations. The legacy organization-project endpoint and an assumed /orgs/zed-pkg/projects/1 URL returned 404; therefore no project number, node ID, or URL is currently claimed.

Organization policy and merge-order documentation is proposed in #11.

Acceptance criteria

  • Use an authorized gh project or GitHub GraphQL session for the zed-pkg organization.
  • Search for an existing Projects v2 board titled exactly zed-pkg-project before creating a duplicate.
  • If absent, create the organization-owned board.
  • Record its verified project number, node ID, URL, owner, and field schema in PROJECT_TRACKING.md.
  • Configure at least these fields: Status, Repository, Linear, Package layer, Release gate, Target branch, Blocked by.
  • Add the active zed-lock hardening/release item, current-main deterministic mise export item, and hardened lock-pin/package-graph follow-up.
  • Link each project item to its GitHub issue or pull request and its corresponding DEN issue.
  • Do not store GitHub tokens, credentials, secret values, or unverified board identifiers in project fields or repository files.

Source-of-truth boundary

Linear owns roadmap/dependency status. GitHub Projects mirrors execution state for repository issues and pull requests. GitHub PR commits, checks, artifacts, and merge records remain the release evidence.

Activity

  1. self-assigned this
    on Aug 5, 2026
  2. ORESoftware commented on Aug 8, 2026

    @ORESoftware
    ContributorAuthor

    Executed 2026-08-08 via a project-scoped GraphQL session (loop-jobs credential; no token material stored anywhere):

    • Authorized GraphQL session for org zed-pkg
    • Searched before creating — the board already existed: zed-pkg-project, org project Provision zed-jetbrains-air as a dedicated Air integration repository #1, node PVT_kwDOEmIPx84BfYhg, https://github.com/orgs/zed-pkg/projects/1 (the 2026-08-05 404 came from the legacy classic-projects REST endpoint; classic projects don't exist for this org)
    • Create — not needed
    • Recorded number/node/URL/owner/schema in PROJECT_TRACKING.md → PR DEN-2875: record verified zed-pkg-project ProjectV2 (org project #1) in PROJECT_TRACKING.md #35
    • Fields configured: Status options aligned to Backlog/Ready/In progress/In review/Blocked/Done; created Linear, Package layer (Interfaces/Clients/Library/CLI/Server/Test/Infra), Release gate (Source review/CI/Artifact/Publish/Certification), Target branch, Blocked by; Repository is built-in
    • Items added with DEN links: zed-interfaces#45 (Backlog; DEN-2862/DEN-2854), zed-cli#131 (In review; DEN-1462), zed-cli#203 (Done; merged), zed-cli#204 (closed unmerged — PROJECT_TRACKING's active merge-train list is stale on this point), draft zed-lock v0.1.1 one-shot publisher (release/v0.1.1) (In progress; DEN-2076/DEN-2503)
    • No tokens/credentials in fields or files

    Note for the owning thread: pre-existing draft items (DEN-1462/1468/1420, issue #21) were left untouched; the DEN-1462 draft duplicates PR #131 and could be consolidated.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions