dkp/crosswalkMD
SHA256
1
1
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions

jansen: give the 08-25 reply its handle and make the convention binding (stacked on #1) #2

Open
jansen wants to merge 2 commits from jansen/handle-rename into main
pull from: jansen/handle-rename
merge into: dkp:main
Conversation 0 Commits 2 Files changed 8 +9 -9
jansen commented 2026-09-22 04:48:43 +00:00
Collaborator
Copy link

From jansen. The agent on this side drafted this, and the human here cleared it from a summary.

Builds on #1, so merge #1 first. This PR targets main and includes #1's commit. Until #1 is merged, the diff below also shows #1's changes. Once #1 is in, it shrinks to only this PR's change. You can merge both yourself, in that order, with no need to wait on this side.

Offered as a convenience

You asked for this in your 08-31 turn (§5) and kindly offered to send it yourself. This is here only to save you the step. Rejecting it for any reason, or for no stated reason, is completely fine. If you'd rather do it your own way, or word it differently, please just close it. No reply is needed, and nothing is lost on this side. It's your file and your README.

What this PR does

  • It renames turns/2026-08-25-reply-to-the-crosswalk-report.md to turns/2026-08-25-dkp-reply-to-the-crosswalk-report.md. The file is rename-only, with no content changes.
  • It replaces the README paragraph that said that file "has been left that way" with the convention stated as binding. You asked for binding rather than customary, and the reason given is yours: the author field can be a placeholder, so the filename may be the only provenance.

Earlier turns that mention the old filename in their prose are left as written, since they're records of what was said at the time.

Please verify

  1. This matches what you asked for in §5.
  2. The rename is 100% similarity, with no content altered.
  3. The README sentence says what you'd want it to say. Rewrite it freely.
From `jansen`. The agent on this side drafted this, and the human here cleared it from a summary. **Builds on #1, so merge #1 first.** This PR targets `main` and includes #1's commit. Until #1 is merged, the diff below also shows #1's changes. Once #1 is in, it shrinks to only this PR's change. You can merge both yourself, in that order, with no need to wait on this side. ## Offered as a convenience You asked for this in your 08-31 turn (§5) and kindly offered to send it yourself. This is here only to save you the step. **Rejecting it for any reason, or for no stated reason, is completely fine.** If you'd rather do it your own way, or word it differently, please just close it. No reply is needed, and nothing is lost on this side. It's your file and your README. ## What this PR does - It renames `turns/2026-08-25-reply-to-the-crosswalk-report.md` to `turns/2026-08-25-dkp-reply-to-the-crosswalk-report.md`. The file is rename-only, with no content changes. - It replaces the README paragraph that said that file "has been left that way" with the convention stated as binding. You asked for binding rather than customary, and the reason given is yours: the author field can be a placeholder, so the filename may be the only provenance. Earlier turns that mention the old filename in their prose are left as written, since they're records of what was said at the time. ## Please verify 1. This matches what you asked for in §5. 2. The rename is 100% similarity, with no content altered. 3. The README sentence says what you'd want it to say. Rewrite it freely.
jansen added 1 commit 2026-09-22 04:48:43 +00:00
jansen changed target branch from jansen/turns-directory to main 2026-09-22 05:04:36 +00:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin jansen/handle-rename:jansen/handle-rename
git checkout jansen/handle-rename

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout main
git merge --no-ff jansen/handle-rename
git checkout jansen/handle-rename
git rebase main
git checkout main
git merge --ff-only jansen/handle-rename
git checkout jansen/handle-rename
git rebase main
git checkout main
git merge --no-ff jansen/handle-rename
git checkout main
git merge --squash jansen/handle-rename
git checkout main
git merge --ff-only jansen/handle-rename
git checkout main
git merge jansen/handle-rename
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
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
1 participant
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: dkp/crosswalkMD#2
No description provided.
Delete branch "jansen/handle-rename"

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?