docs: point at the dejima organization #102

Merged

branderson merged 2 commits from org-move into main 2026-08-08 20:34:09 -07:00

Conversation 1 Commits 2 Files Changed 3

+5 -5

dejima-agent commented 2026-08-08 19:16:56 -07:00

Collaborator

Copy Link

Copy Source

Summary generated by LLM agent

dejima and dejima-ci-hardener have both moved out of the personal namespace into a dejima organization, so every link into either one was a path segment wrong: four to dejima-ci-hardener, one to this repository's own issue #97.

Gitea redirects the old paths, so none of these were broken. They were only lying about where the thing lives — which is the kind of stale that survives indefinitely, because nothing ever fails to draw attention to it.

README.md	2 links to dejima-ci-hardener
docs/ci.md	2 links to dejima-ci-hardener
docs/configuration.md	1 link to issue #97

Only the organization segment changes. The host stays gitbox.branderson.io, which is what a reader resolves.

Nothing in the code had to change

No file under bin/, test/ or .gitea/ referenced the old owner. The forge CLIs read owner and repo out of the git remote rather than from anything committed, which is why moving a repository does not require a code change to keep gitea-pr and friends working — and why this PR is documentation only.

The git remote itself has been repointed at dejima/dejima, and this branch was pushed through it, so that path is confirmed live rather than assumed.

Testing

364 green across static, config, providers. runtime.bats not run: no Docker in a dejima sandbox, and nothing here touches it.

Note on #101

Both this and #101 touch docs/ci.md, on different lines — #101 changes a runs-on: label in prose, this changes the hardener URLs. They merge cleanly in either order; whichever goes second may want a rebase for tidiness rather than for correctness.

**Summary generated by LLM agent** dejima and dejima-ci-hardener have both moved out of the personal namespace into a `dejima` organization, so every link into either one was a path segment wrong: four to dejima-ci-hardener, one to this repository's own issue #97. Gitea redirects the old paths, so none of these were broken. They were only lying about where the thing lives — which is the kind of stale that survives indefinitely, because nothing ever fails to draw attention to it. | | | | --- | --- | | `README.md` | 2 links to dejima-ci-hardener | | `docs/ci.md` | 2 links to dejima-ci-hardener | | `docs/configuration.md` | 1 link to issue #97 | Only the organization segment changes. The host stays `gitbox.branderson.io`, which is what a reader resolves. ## Nothing in the code had to change No file under `bin/`, `test/` or `.gitea/` referenced the old owner. The forge CLIs read owner and repo out of the git remote rather than from anything committed, which is why moving a repository does not require a code change to keep `gitea-pr` and friends working — and why this PR is documentation only. The git remote itself has been repointed at `dejima/dejima`, and this branch was pushed through it, so that path is confirmed live rather than assumed. ## Testing 364 green across `static`, `config`, `providers`. `runtime.bats` not run: no Docker in a dejima sandbox, and nothing here touches it. ## Note on #101 Both this and #101 touch `docs/ci.md`, on different lines — #101 changes a `runs-on:` label in prose, this changes the hardener URLs. They merge cleanly in either order; whichever goes second may want a rebase for tidiness rather than for correctness.

dejima-agent added 1 commit 2026-08-08 19:16:57 -07:00

docs: point at the dejima organization ... e69d35a8a4

Both repositories moved out of the personal namespace and into a `dejima`
organization, so every link into either one is now one path segment wrong:
four to dejima-ci-hardener and one to this repository's own issue #97.

Gitea redirects an old path, so none of these were broken. They were merely
lying about where the thing lives, which is the kind of stale that survives
indefinitely because nothing fails.

Only the organization segment changes. The host stays `gitbox.branderson.io`,
which is the name a reader resolves; the git remote uses the internal
`gitbox.bradina.localdomain` and is not a documentation concern.

Nothing in `bin/`, `test/` or the workflow hardcoded the old owner, so this is
documentation only. The forge CLIs read owner and repo out of the git remote
rather than from anything committed here, which is why moving a repository
does not require a code change to keep them working.

branderson added 1 commit 2026-08-08 20:19:08 -07:00

Merge branch 'main' into org-move 32589c0603

branderson approved these changes 2026-08-08 20:34:01 -07:00

branderson merged commit 9cb6b7b432 into main 2026-08-08 20:34:09 -07:00

branderson referenced this issue from a commit 2026-08-08 20:34:11 -07:00

Merge pull request 'docs: point at the dejima organization' (#102) from org-move into main

Sign in to join this conversation.

Reviewers

No Reviewers

branderson

Labels

Clear labels

Compat/Breaking

Breaking change that won't be backward compatible

Kind/Bug

Something is not working

Kind/Documentation

Documentation changes

Kind/Enhancement

Improve existing functionality

Kind/Feature

New functionality

Kind/Security

This is security issue

Kind/Testing

Issue or pull request related to testing

Priority

Critical

1

The priority is critical

Priority

High

2

The priority is high

Priority

Low

4

The priority is low

Priority

Medium

3

The priority is medium

Reviewed

Confirmed

1

Issue has been confirmed

Reviewed

Duplicate

2

This issue or pull request already exists

Reviewed

Invalid

3

Invalid issue

Reviewed

Won't Fix

3

This issue won't be fixed

Status

Abandoned

3

Somebody has started to work on this but abandoned work

Status

Blocked

1

Something is blocking this issue or pull request

Status

Need More Info

2

Feedback is required to reproduce issue or to continue work

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

branderson dejima-agent

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dejima/dejima#102