Sitelet https://github.com/devantler-tech/.github/issues/240
Skip to content

Archive devantler-tech/actions once nothing references it #240

Description

@devantler

🤖 Generated by the Agentic Engineer

Evidence

#164's success signal is that devantler-tech/actions is archived and no non-archived repository references it. devantler-tech/reusable-workflows went the same way through deploy/archived-repositories/ and its three-phase lifecycle.

Acceptance criteria

  • An organization-wide search, checked against a known reference as a control, finds no non-archived repository referencing devantler-tech/actions, and no organization ruleset names repository 948529001.
  • Any open issues still on actions have been transferred and any open pull requests closed (Freeze devantler-tech/actions once the catalogue lives in .github #236).
  • actions is archived through deploy/archived-repositories/, the same way reusable-workflows was, and its repository-specific deploy/ entries move to their archived lifecycle.
  • profile/ and workflow-templates/ still work after the move.

Blocked by #237 and #239.

Activity

  1. added theissue type on Sep 25, 2026
  2. moved this to 📥 Backlog in 🌊 Project Boardon Sep 25, 2026
  3. devantler commented on Oct 2, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Refreshed the archival gates on 2026-10-02. Legacy Actions is still public and unarchived. Complete native inventory finds zero open PRs and one open issue, actions #1389, which intentionally tracks a necessary release backport of catalogue #389 while consumers remain on the legacy source.

    Required-workflow readback still points five workflow families at legacy Actions (#237), and catalogue CD still calls its publisher (#242). These are active dependencies, so neither the consumer nor inventory acceptance gate is met. The backport issue needs delivery or an explicit migration disposition; it is not obsolete metadata to close blindly.

    Blocker: required-workflow and publisher migration, legacy issue disposition, and declarative lifecycle/profile verification. Archive only after those gates have readback evidence.

  4. devantler commented on Oct 4, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Verified retirement prerequisites — 2026-10-04

    The native paginated legacy intake is empty: zero open issues and zero open pull requests, re-read at 11:13 UTC. The repository remains active and public. This completes the intake prerequisite, not the archive gate.

    The complete public metadata census still finds 62 direct legacy declarations in 18 consumers and 70 legacy required-workflow declarations across 22 public default branches, rebound through 11:17:32 UTC. Administrative organization-ruleset coverage remains UNKNOWN under the current authority. Canonical publisher acceptance also remains blocked by #242. Archiving now would break required checks and publishers.

    After #237, #239 and #242 clear, join the final complete active universe with source/rule/publisher evidence and known positive controls. Apply the reviewed three-phase archived-repository lifecycle, then read back the repository's archived state and verify profile and workflow-template behavior. No archive or settings change was made in this observation.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions