Close the GitHub copy open issue in the Project Plan #26

Merged
Tirsvad merged 2 commits from plan-close-github-copy-issue into main 2026-10-08 13:06:10 +02:00
Owner

Close the GitHub copy open issue in the Project Plan

The Project Plan listed the GitHub copy of this repository as an open issue: it had no description or topics, and S01 was asked whether the same workflow as in the day-20 repository applies. When the copy was checked on 2026-10-08 it already showed the same description and topics as the Gitea repository. This project did not set them. So the open issue is stale.

What is in the pull request

  • docs/project-plan.md: the Open Issues entry is closed, with the date, the observation and the reason that no task is added. A new Version History row records it, Accepted by S01 in chat; the oldest row is dropped so the table keeps the two latest rows.
  • A follow-up commit resolves the pending commit link of the new row.

Only that one file changes. No source, test or other document is touched.

Notes for the reviewer

  • The entry says the project did not set the description and topics on the GitHub copy. It does not say how they got there: the day-20 repository relies on a workflow on the git host, but this was not confirmed for this repository.
  • The plan has no QC checklist, so there is no review record; the acceptance is S01's instruction in chat.

No issue closed: this is a correction of a document and has no task row. Issues #14 (play the game) and #22 (compare with the lecture video) stay open for S01.

## Close the GitHub copy open issue in the Project Plan The Project Plan listed the GitHub copy of this repository as an open issue: it had no description or topics, and S01 was asked whether the same workflow as in the day-20 repository applies. When the copy was checked on 2026-10-08 it already showed the same description and topics as the Gitea repository. This project did not set them. So the open issue is stale. ### What is in the pull request - `docs/project-plan.md`: the Open Issues entry is closed, with the date, the observation and the reason that no task is added. A new Version History row records it, `Accepted` by S01 in chat; the oldest row is dropped so the table keeps the two latest rows. - A follow-up commit resolves the `pending` commit link of the new row. Only that one file changes. No source, test or other document is touched. ### Notes for the reviewer - The entry says the project did not set the description and topics on the GitHub copy. It does not say how they got there: the day-20 repository relies on a workflow on the git host, but this was not confirmed for this repository. - The plan has no QC checklist, so there is no review record; the acceptance is S01's instruction in chat. No issue closed: this is a correction of a document and has no task row. Issues #14 (play the game) and #22 (compare with the lecture video) stay open for S01.
Tirsvad added 2 commits 2026-10-08 13:05:41 +02:00
The GitHub copy of the repository already shows the same description and topics as the Gitea repository. This project did not set them; in the day-20 repository a workflow on the git host does, so no task is added. The Version History gets a row, accepted by S01 in chat.
Resolve pending commit links
CI / checks (push) Successful in 48s
CI / checks (pull_request) Successful in 46s
cf5c488f20
Replaces pending in the Version History of the Project Plan with a link to the commit that introduced the row.
Tirsvad merged commit a02db57494 into main 2026-10-08 13:06:10 +02:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Tirsvad-Udemy-100-days-of-code/021-snake-game#26