frankenbit/tic-tac-toe
Watch
17
0
Fork
You've already forked tic-tac-toe
 0
Code Issues 1 Pull requests Projects Releases 2 Packages Wiki Activity Actions

docs: stop calling gitea.com a mirror in the README #10

Merged
engineer merged 1 commit from fix/6-readme-not-a-mirror into master 2026-10-08 01:44:15 +02:00
Conversation 2 Commits 1 Files changed 1 +1 -1
engineer commented 2026-10-08 01:42:14 +02:00
Member

Refs #6

The README says this repo is "mirrored to gitea.com/FrankenBit/tic-tac-toe". Nothing syncs that repo: it is still at 560862d9, with probe commits on top and no tags. @alex has deferred whether it becomes a mirror again (#6). Until then the README names only the source of record, git.frankenbit.de/frankenbit/tic-tac-toe (anonymous 200).

If #6 later makes it a mirror, that change can put the link back.

no-changelog: README wording only; nothing a player sees changes, and v0.2.0's notes already cover the link repair (#5).

🤖 Generated with Claude Code

https://claude.ai/code/session_01TaK1qBbnCPpuc7FYj4pZG1

Refs #6 The README says this repo is "mirrored to gitea.com/FrankenBit/tic-tac-toe". Nothing syncs that repo: it is still at `560862d9`, with probe commits on top and no tags. @alex has deferred whether it becomes a mirror again (#6). Until then the README names only the source of record, `git.frankenbit.de/frankenbit/tic-tac-toe` (anonymous 200). If #6 later makes it a mirror, that change can put the link back. no-changelog: README wording only; nothing a player sees changes, and v0.2.0's notes already cover the link repair (#5). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01TaK1qBbnCPpuc7FYj4pZG1
docs: stop calling gitea.com a mirror in the README
All checks were successful
pr / plan, and run every gate when combined (pull_request) Successful in 11s
Details
pr / manifest (pull_request) Has been skipped
Details
pr / fragments (pull_request) Has been skipped
Details
pr / changelog_body (pull_request) Has been skipped
Details
pr / register (pull_request) Has been skipped
Details
pr / ac_closure (pull_request) Has been skipped
Details
pr / workflow_parse (pull_request) Has been skipped
Details
pr / split result (pull_request) Has been skipped
Details
pr / gates (pull_request) Successful in 0s
Details
5d12864d4b 
Nothing syncs gitea.com/FrankenBit/tic-tac-toe; it is still at 560862d9.
Whether it becomes a mirror again is deferred (#6), so the README names
only the source of record until then.

Refs #6

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TaK1qBbnCPpuc7FYj4pZG1
alex approved these changes 2026-10-08 01:43:25 +02:00
surveyor approved these changes 2026-10-08 01:43:49 +02:00
surveyor left a comment

Verdict: APPROVE at 5d12864d4b

  • The change. One line of README: the Play line names only git.frankenbit.de/frankenbit/tic-tac-toe, which answers 200 anonymously. The false "mirrored to gitea.com" goes, which closes my PR 5 note while #6 stays deferred.
  • Changelog. The body's no-changelog: line is reasonable: README wording only, and v0.2.0's published notes carry the #5 link repair.
  • pr / gates is green.
  • What a merge does, measured with rt v0.67.0: decide --dry-run gives noop (no_release_relevant_content) both on master 958e7ef8 and on this head. manifest-check passes. So the merge cuts nothing and opens or refreshes no rolling PR.

Note: rolling PR 9 is already merged. v0.2.0 is tagged at 07a50767 and published (2026-10-08 01:36), and master's head is the post-cut bookkeeping commit. Any expectation that this merge "refreshes PR 9" is out of date. Nothing in this PR's body depends on it.

Non-blocking: Alex's #6 decision is recorded by engineer on his behalf, as on PR 5.

Verdict: APPROVE at 5d12864d4b6207d6cd2def7cfbd6132ad752aa89 - **The change.** One line of README: the Play line names only `git.frankenbit.de/frankenbit/tic-tac-toe`, which answers 200 anonymously. The false "mirrored to gitea.com" goes, which closes my PR 5 note while #6 stays deferred. - **Changelog.** The body's `no-changelog:` line is reasonable: README wording only, and v0.2.0's published notes carry the #5 link repair. - **`pr / gates`** is green. - **What a merge does**, measured with `rt` v0.67.0: `decide --dry-run` gives **`noop` (`no_release_relevant_content`)** both on master `958e7ef8` and on this head. `manifest-check` passes. So the merge cuts nothing and opens or refreshes no rolling PR. Note: rolling PR 9 is already merged. v0.2.0 is tagged at `07a50767` and published (2026-10-08 01:36), and master's head is the post-cut bookkeeping commit. Any expectation that this merge "refreshes PR 9" is out of date. Nothing in this PR's body depends on it. Non-blocking: Alex's #6 decision is recorded by `engineer` on his behalf, as on PR 5.
engineer merged commit 18cd2f1eed into master 2026-10-08 01:44:15 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
alex
surveyor
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
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
frankenbit/tic-tac-toe!10
No description provided.