Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Decision: archive or generate the dead GitHub Actions twin

Open
  • Is something wrong?
#457 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, go, python
Domain
build-system, devops

Research direction

Read the .github/workflows/ release-pipeline twin, the live ngit lane, and ngit-gen-shards.py alongside packaging/ngit-release-matrix.json. The issue recommends archiving the twin but leaves the choice to a maintainer, so confirm the decision before making changes. Done means the chosen archive-or-generate approach is applied and the obsolete drift surface is addressed.

Written by the indexing model from the issue text.

Description

Summary

.github/workflows/ still carries the pre-shard release-pipeline twin (build-package monolith, repro-check, test) for a runner that has been queue-dead org-wide since 2026-08-27 (newest run anywhere: a 2026-09-17 "Graph Update" still queued — verified during the #448 review round). The live pipeline is the ngit lane, which #445 restructured into generated shards + a driven orchestrator that the twin does not mirror.

The twin is now pure drift surface: every release-infra improvement (manifest-derived Go pins, mirror-list changes, timeout philosophy, gate wiring) must either be done twice or knowingly skipped on a lane that cannot run. Two concrete divergences already exist: the twin keeps blossom1.orangesync.tech (deliberate, documented) and its gate wiring predates #435's both-publisher default era.

Options

  1. Archive — move to .github/workflows-archive/ (or delete with a README pointer at the ngit lane). History stays greppable; the drift surface disappears; check-mirror-sync.py (#456) loses its one documented exclusion. Cheapest to maintain; costs revival effort if Actions ever comes back org-wide.
  2. Generate — add the twin's release workflow to ngit-gen-shards.py's output so both lanes render from packaging/ngit-release-matrix.json. Keeps a revival path warm; costs generator complexity for a lane that cannot currently run anything.
  3. Status quo — accept the drift surface and the double-touch cost.

Recommendation

Archive (option 1), revisit if the org restores Actions. Not urgent for the v0.6.0 tag — the twin cannot affect a release it cannot run — but it doubles the cost of every DRY improvement landing now (this surfaced while single-sourcing the mirror lists).

Maintainer decision; no change made.

Dominant language
Go
Stars
12
Forks
14
Avg merge
1d 6h
Merged PRs (30d)
211

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenTollGate/tollgate-module-basic-go

All issues in OpenTollGate/tollgate-module-basic-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.