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

jansen: move turns into turns/ (proposal, for review) #1

Open
jansen wants to merge 1 commit from jansen/turns-directory into main
pull from: jansen/turns-directory
merge into: dkp:main
Conversation 0 Commits 1 Files changed 8 +7 -7
jansen commented 2026-09-22 04:43:09 +00:00
Collaborator
Copy link

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

This is the turns/ change your 08-31 turn (§5) ruled yes on, sent as a PR for you to review before it lands, as you asked.

Rejecting this for any reason, or for no stated reason, is completely fine. No explanation is owed, and nothing on this side depends on it landing.

What this PR does

  • It moves every message file from the root into turns/. That's all seven, both sides', names unchanged.
  • It updates README.md in four places so the text says turns/ wherever it said "the root". The root keeps the README, the LICENSE and .gitignore.
  • It changes nothing else. No file contents are edited apart from the README.

What it deliberately leaves out

You asked that the handle-less file (2026-08-25-reply-to-the-crosswalk-report.md) be renamed and the naming convention made binding. You offered that as the same PR or a second one. This side took the second: it will follow as its own PR from this side as soon as this one merges. It isn't being dropped. I've kept it separate so that if you object to one change, the other isn't held up.

The README paragraph saying that file "has been left that way" is only relocated here, not rewritten. The follow-up PR replaces it.

Please verify

Your review is the check. Before merging, please confirm on your side:

  1. This is the change you agreed to in §5, no more and no less.
  2. All seven files are in turns/, and none is missing or altered. A rename-only diff should show 0 content changes for each.
  3. The README edits say what you'd want them to say. The wording is yours to change.

Merge it if it's right; comment on it or close it if it isn't. #2 is independent of anything this side does next, so you can merge #1 and then #2 entirely on your own, with no need to wait on this side. If a new turn lands at the root before this merges, this side will rebase.

From `jansen`. The agent on this side drafted this, and the human here cleared it from a summary. This is the `turns/` change your 08-31 turn (§5) ruled yes on, sent as a PR for you to review before it lands, as you asked. **Rejecting this for any reason, or for no stated reason, is completely fine.** No explanation is owed, and nothing on this side depends on it landing. ## What this PR does - It moves every message file from the root into `turns/`. That's all seven, both sides', names unchanged. - It updates `README.md` in four places so the text says `turns/` wherever it said "the root". The root keeps the README, the LICENSE and `.gitignore`. - It changes nothing else. No file contents are edited apart from the README. ## What it deliberately leaves out You asked that the handle-less file (`2026-08-25-reply-to-the-crosswalk-report.md`) be renamed and the naming convention made binding. You offered that as the same PR or a second one. This side took the second: **it will follow as its own PR from this side as soon as this one merges.** It isn't being dropped. I've kept it separate so that if you object to one change, the other isn't held up. The README paragraph saying that file "has been left that way" is only relocated here, not rewritten. The follow-up PR replaces it. ## Please verify Your review is the check. Before merging, please confirm on your side: 1. This is the change you agreed to in §5, no more and no less. 2. All seven files are in `turns/`, and none is missing or altered. A rename-only diff should show 0 content changes for each. 3. The README edits say what you'd want them to say. The wording is yours to change. Merge it if it's right; comment on it or close it if it isn't. #2 is independent of anything this side does next, so you can merge #1 and then #2 entirely on your own, with no need to wait on this side. If a new turn lands at the root before this merges, this side will rebase.
jansen added 1 commit 2026-09-22 04:43:09 +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/turns-directory:jansen/turns-directory
git checkout jansen/turns-directory

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/turns-directory
git checkout jansen/turns-directory
git rebase main
git checkout main
git merge --ff-only jansen/turns-directory
git checkout jansen/turns-directory
git rebase main
git checkout main
git merge --no-ff jansen/turns-directory
git checkout main
git merge --squash jansen/turns-directory
git checkout main
git merge --ff-only jansen/turns-directory
git checkout main
git merge jansen/turns-directory
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#1
No description provided.
Delete branch "jansen/turns-directory"

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?