Skip to content

Retire github-workflows after ownership migrations #180

Description

@vitormattos

Goal

Retire this repository after its active responsibilities move to their natural owners.

This migration must not preserve legacy code for compatibility by default. Anything not used by the target architecture should be removed here, not copied elsewhere.

Destination epics

Expected disposition

Move to release-tool

Only current release-product responsibilities:

  • release lifecycle Actions and helpers that remain part of the target product;
  • release-specific behavior that is first characterized and then incorporated into PHP;
  • release-specific tests that remain useful;
  • current release product documentation;
  • release Action/versioning responsibilities.

Do not preserve helper Actions, scripts or compatibility entry points merely because they exist today. If the PHP architecture absorbs them, delete the old implementation after parity is proven.

Move to LibreCodeCoop/.github

Only current organization-catalog responsibilities:

  • current organization workflow templates and required metadata;
  • upstream Nextcloud vendoring/pins that are still used;
  • current organization patches;
  • upstream refresh/render/policy tooling that remains necessary;
  • catalog and synchronization tests that validate the target architecture;
  • sync-workflows Action;
  • first-merged-pr-comment Action and documentation;
  • current workflow adoption/dependency/cross-repository catalog documentation.

Delete rather than migrate

  • workflow-templates/release-nextcloud-app.yml, its metadata and any tests/docs/references that only describe that retired workflow;
  • catalog publication machinery that exists only for the github-workflows → .github hop;
  • sync_catalog.py once the publication hop is removed;
  • this repository's independent VERSION/release machinery once no public components remain here;
  • stale generated outputs;
  • obsolete architecture documentation;
  • superseded reusable workflow experiments or compatibility paths not used by the target design;
  • tests whose only purpose is validating removed behavior;
  • any other legacy file discovered during the migration that has no current consumer or target responsibility.

Known consumer references to migrate or remove

A current organization-wide search found references to LibreCodeCoop/github-workflows in:

  • LibreCodeCoop/extract workflow files;
  • LibreCodeCoop/profile_fields workflow files, including the old release-nextcloud-app.yml;
  • LibreSign/libresign release, nightly, sync, metadata and first-merged-PR workflows;
  • LibreSign/documentation release-process documentation.

These references must be reviewed individually. References to current functionality should be repointed to their new owner; references to retired functionality should be removed rather than redirected to a compatibility shim.

Final checks before archival

  • Search both LibreCodeCoop and LibreSign organizations for remaining LibreCodeCoop/github-workflows references.
  • Search for retired workflow names such as release-nextcloud-app.
  • Update current consumer workflows/templates to their new immutable Action pins.
  • Remove retired consumer workflows instead of migrating them.
  • Confirm catalog synchronization works directly from .github.
  • Confirm release workflows use release-tool Actions.
  • Confirm no current release or workflow process depends on this repository.
  • Confirm no legacy compatibility layer was introduced solely to keep obsolete paths working.
  • Archive/read-only this repository only after those checks pass.

Activity

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

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions