chore: track tickets on Forgejo instead of GitHub #57
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/tickets-on-forgejo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Tickets are tracked on Forgejo again.
CLAUDE.mdand the ticket, kickoff, work-queue and ship-it skills now usefjfor every issue action, and commits and MRs cite a ticket asRefs #<N>. The open GitHub tickets were carried over with their labels and comments: GH-3 is #54, GH-4 is #55, GH-6 is #56. The GitHub originals are closed with a pointer.Refs #54 #55 #56
Verification
Docs and skills only, so
make checkhas nothing new to exercise. Checked by hand:ghorBparsons0904references remain inCLAUDE.mdor the ticket skillsfj issue create,edit labels,commentandviewworked on the three carried ticketsDocs
The Claude cloud flow still runs through the GitHub mirror, but cloud sessions can't read Forgejo tickets, so
CLAUDE.mdnow says the PM pastes them the brief. The mirror workflows are unchanged.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ddd6CjE5eQRWm7JmEjqXNf