MacKwnoX/Bike-Tinder
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[TEST] Acceptance run - README deployment section is stale #1

New Issue
Closed
opened 2026-11-13 14:58:00 -04:00 by AlexanderRozhenko · 1 comment
AlexanderRozhenko commented 2026-11-13 14:58:00 -04:00
Collaborator
Copy Link

Automated-pipeline acceptance test filed by AlexanderRozhenko. Intent: give the new issue pipeline one safe, real, docs-only task, end to end.

Problem: README.md is stale in two places:

  • The Status line (~line 5) says deployment "awaits the one-time Tailscale sidecar authorization" - the sidecar was authorized and the private phone URL is in use.
  • The "## Deployment (planned)" section (~line 134) still reads as planned - the podman stack has been live since 2026-11-12 (runs under podman-stack-bike-tinder.service; nightly import + agent read + DB backup armed).

Ask: update README.md so it reflects current reality (deployed 2026-11-12; stack unit; nightly chain; phone URL in use). Docs only - no code changes - commit with a docs: message.

Acceptance: README states the deployed reality accurately; no other files touched. No deployment is needed for a docs-only change; closing this issue automatically once the fix lands on dev is fine.

Automated-pipeline acceptance test filed by AlexanderRozhenko. Intent: give the new issue pipeline one safe, real, docs-only task, end to end. Problem: `README.md` is stale in two places: - The Status line (~line 5) says deployment "awaits the one-time Tailscale sidecar authorization" - the sidecar was authorized and the private phone URL is in use. - The "## Deployment (planned)" section (~line 134) still reads as planned - the podman stack has been live since 2026-11-12 (runs under `podman-stack-bike-tinder.service`; nightly import + agent read + DB backup armed). Ask: update `README.md` so it reflects current reality (deployed 2026-11-12; stack unit; nightly chain; phone URL in use). Docs only - no code changes - commit with a `docs:` message. Acceptance: README states the deployed reality accurately; no other files touched. No deployment is needed for a docs-only change; closing this issue automatically once the fix lands on `dev` is fine.
AlexanderRozhenko commented 2026-11-13 15:02:00 -04:00
Author
Collaborator
Copy Link

Picked this up. Root cause: README.md was last updated before the P4 cutover and never revisited — the status line still said the Tailscale sidecar "awaits the one-time authorization", and the deployment section was still headed "planned".

Changed (README.md only, commit 618cd4a on dev):

  • Status paragraph now reflects the live reality: stack live since 2026-11-12 under podman-stack-bike-tinder.service, sidecar authorized 2026-11-12 with the private phone URL in use, and v1.1.0 deployed + released 2026-11-13.
  • Deployment section retitled "Deployment (live)": stack unit, authorized sidecar, and the nightly chain — catalog import → agent read → DB backup (14-deep).
  • Two small accuracy fixes while in the file: the B1 line no longer reads as "built on dev" (it shipped 2026-11-11), and the self-check comment now says 35 checks (was 25).

Checks: app.selfcheck 35/35 green on the fixed tree; no other files touched. Docs-only change, no deploy needed. Closing.

Picked this up. Root cause: `README.md` was last updated before the P4 cutover and never revisited — the status line still said the Tailscale sidecar "awaits the one-time authorization", and the deployment section was still headed "planned". Changed (`README.md` only, commit `618cd4a` on `dev`): - Status paragraph now reflects the live reality: stack live since 2026-11-12 under `podman-stack-bike-tinder.service`, sidecar authorized 2026-11-12 with the private phone URL in use, and v1.1.0 deployed + released 2026-11-13. - Deployment section retitled "Deployment (live)": stack unit, authorized sidecar, and the nightly chain — catalog import → agent read → DB backup (14-deep). - Two small accuracy fixes while in the file: the B1 line no longer reads as "built on dev" (it shipped 2026-11-11), and the self-check comment now says 35 checks (was 25). Checks: `app.selfcheck` 35/35 green on the fixed tree; no other files touched. Docs-only change, no deploy needed. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
AlexanderRozhenko MacKwnoX
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MacKwnoX/Bike-Tinder#1
Delete Branch "%!s()"

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?