fix: repoint the stale Codeberg org link and unlink pre-migration issue numbers - #215
Merged
Merged
Conversation
…ue numbers GitHub is the only host for this org; Codeberg was a mirror and is not used, including for issues. In this repo the honest scope turned out to be small, because most of the ~415 "codeberg" occurrences are not stale links at all — they are a shipped feature. Changed (5 files): - docs/static/llms.txt — the Contact block still advertised `Codeberg: https://codeberg.org/Conduction` directly under a Source code line that already pointed at github.com/ConductionNL/versioniq. Now `GitHub: https://github.com/ConductionNL`. - Four `[issue #24](codeberg…/app-versions/issues/24)` links in openspec proposals and specs lost their URL and kept the fact as plain text. Issue-number decision: Codeberg issue numbers do NOT correspond to GitHub issue numbers, and this repo proves it. The four archived plan.json records point at Codeberg issues #10, #11, #12 and #13 (improve-install-failure-diagnostics, move-to-admin-settings, codeberg-forge-support, surface-external-sources-ui). On GitHub those same numbers are Dependabot dependency-bump PRs. Host-swapping those URLs would have made every archived change record cite an unrelated Dependabot bump — so all four plan.json files are left untouched, also because each carries `"tracking_issue": <n>` and `"tracker": "codeberg"` beside the URL. Issue #24 was checked the same way and does correspond ("Add public Software Catalogus as a discovery source"), but the rule was applied uniformly and the correspondence is recorded in the text instead of as a link. NOT changed, deliberately — Codeberg is a supported forge in this app, not a dead mirror. `ForgeRegistry::FORGE_CODEBERG` is live production config (api, web and tokenCreateUrl), and codeberg.org still serves it. Rewriting any of it would break the feature. See the PR body for the full list, including the `.forgejo/` directory, which is kept.
Contributor
Quality Report — ConductionNL/versioniq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| composer | ✅ | ✅ 29/29 | |||
| npm | ✅ | ✅ 282/282 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | ✅ | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-08-24 10:14 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub is the only host for this org — Codeberg was a mirror and is not used, including for issues.
The honest headline: in this repo, almost none of the ~415
codebergoccurrences are stale links. Codeberg is a supported forge feature of Versioniq, backed by live production config, live specs, PHPUnit tests and Playwright e2e fixtures.codeberg.orgstill serves that API. Rewriting any of it would break a shipped feature, not fix a dead link.So the real scope was 5 files, 5 lines.
Counts by category
codeberg.org/Conductionin the docs Contact blockgithub.com/ConductionNL[issue #24](…/app-versions/issues/24)in openspec proposals/specstracking_issue_urlin archivedplan.jsoncodeberg.org/api/v1,/user/settings/applications,codeberg.orgweb base)'codeberg',codeberg:{owner}/{repo})The issue-number decision — and the proof
The rule is that Codeberg issue numbers do not correspond to GitHub issue numbers. This repo demonstrates it exactly. The four archived
plan.jsonrecords point at Codeberg issues #10–#13. I resolved those same numbers on GitHub:ConductionNL/versioniqon GitHubchore(deps): Bump vue from 3.5.29 to 3.5.32chore(deps-dev): Bump rector/rector …chore(deps-dev): Bump vite from 7.3.1 to 8.0.8chore(deps-dev): Bump rector/rector …Host-swapping those URLs would have made every archived change record cite an unrelated Dependabot bump. They are left untouched — reinforced by the fact that each record carries
"tracking_issue": <n>and"tracker": "codeberg"as separate fields right beside the URL, so a repointed URL would contradict its own siblings.Issue #24 was checked the same way and does correspond — GitHub
versioniq#24is "Add public Software Catalogus (softwarecatalog) as a discovery source", matching the sentence. I still applied the rule uniformly and removed the URL, but recorded the verified correspondence in the text so a reviewer can restore a link deliberately rather than by assumption.Verification
codeberghits reviewed; every one is a deliberate keep (categorised above).https://github.com/ConductionNL→ 200 (curl -L).plan.jsonfiles re-parsed withjson.loadafter the change → valid (they were not modified).lib/were touched, so no PHPCS run was needed; no JS/YAML touched either. Diff is 5 insertions / 5 deletions.## Notesbullet, not inside aWHEN/THENrequirement block, so no spec semantics changed.Left alone deliberately — needs a human decision
lib/Service/Source/ForgeRegistry.php—public const FORGE_CODEBERG = 'codeberg'withapi => https://codeberg.org/api/v1,web => https://codeberg.org,tokenCreateUrl => https://codeberg.org/user/settings/applications. Live production config for a supported forge.openspec/specs/external-sources/spec.mdandopenspec/specs/pat-management/spec.md— containMUSTrequirements that mandate those exact Codeberg URLs.ForgeRegistryTest.phpassertshttps://codeberg.org/api/v1;InstallerServiceTrustedPatternTest.phpasserts the trusted patterncodeberg:Conduction/openregister;ForgeReleaseSourceTest.phpassertshttps://codeberg.org/api/v1/repos/Conduction/pipelinq/releases; plustests/e2e/fixtures/forge/server.mjsand the PAT e2e specs. A spec + test pair that mandates the word should not be inverted by a link sweep..forgejo/— kept, not deleted. Contains four issue templates andworkflows/documentation.yml. ℹ️ It does not reference aCODEBERG_TOKENsecret (I checked).2026-06-14-codeberg-forge-support/— the whole change (proposal, design, tasks, specs) documenting how Codeberg support was built. Historical record.docs/tutorials/admin/03-github-source.md— user documentation for the feature, including thecodeberg:{owner}/{repo}binding syntax an admin actually types.Worth a follow-up issue (out of scope here)
Several live specs and tests still use pre-rename org/repo names inside Codeberg example URLs —
Conduction/openregister,Conduction/pipelinq. They are illustrative examples inside forge requirements, coupled to assertions in PHPUnit, so changing them is a spec change rather than a link fix.Note on authorship: this repo has no local git identity, so the global one (
Conduction Release Bot) would have been used. I set the commit author to Ruben to match the sibling PR inconduction-website; say the word if you'd prefer the bot identity.