coilyco-flight-deck/otel-a2a-relay-cli
Archived
2
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

Add mirror-to-github workflow #4

New issue
Closed
opened 2026-06-03 00:11:03 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-06-03 00:11:03 +00:00
Owner
Copy link

Problem

Forgejo is canonical for o2r, but there is no GitHub mirror workflow. coily and the other flight-deck Go CLIs push main + tags to a read-only GitHub mirror on every push.

Goal

Add .forgejo/workflows/mirror-to-github.yml, ported from coilysiren/coily. Triggers on push to main and v* tags, force-pushes both to the GitHub mirror, and no-ops cleanly when the GITHUB_MIRROR_PAT secret is absent so it can land before the secret is provisioned.

Open question

  • Does a coilysiren/otel-a2a-relay-cli (or coilyco-flight-deck) GitHub mirror repo exist yet? If not, create it as part of this ticket and wire GITHUB_MIRROR_PAT. The README install path stays Forgejo-direct-tap regardless.

Part of the o2r packaging parity epic.

## Problem Forgejo is canonical for o2r, but there is no GitHub mirror workflow. coily and the other flight-deck Go CLIs push main + tags to a read-only GitHub mirror on every push. ## Goal Add `.forgejo/workflows/mirror-to-github.yml`, ported from coilysiren/coily. Triggers on push to `main` and `v*` tags, force-pushes both to the GitHub mirror, and no-ops cleanly when the `GITHUB_MIRROR_PAT` secret is absent so it can land before the secret is provisioned. ## Open question - Does a `coilysiren/otel-a2a-relay-cli` (or coilyco-flight-deck) GitHub mirror repo exist yet? If not, create it as part of this ticket and wire `GITHUB_MIRROR_PAT`. The README install path stays Forgejo-direct-tap regardless. Part of the o2r packaging parity epic.
coilysiren commented 2026-06-17 08:23:42 +00:00
Author
Owner
Copy link

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:23:43 +00:00
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
chore/code-comments-cleanup
v0.2.0
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/otel-a2a-relay-cli#4
No description provided.