Skip to content

sync: port four Codeberg-only commits to GitHub - #118

Merged
rubenvdlinde merged 4 commits into
mainfrom
sync/codeberg-to-github
Aug 2, 2026
Merged

sync: port four Codeberg-only commits to GitHub#118
rubenvdlinde merged 4 commits into
mainfrom
sync/codeberg-to-github

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Codeberg is a backup mirror; GitHub is primary. Four commits landed only on Codeberg and are ported here.

What was genuinely missing

commit brings
8651b05 docs/claude/skill-level-sources.md (+212), README + writing-skills updates
a67bb4a docker/php/zz-conduction-opcache.ini (+37) — PHP JIT disabled, ~140 ms off every request
481acff compose mounts decidesk/openbuild/petstore/hrmq/shillinq from their real checkouts
3f3f37c compose warning that the file needs -p openregister

Net: +297 lines, all additive.

What was deliberately NOT ported

Four Codeberg ci(quality) commits (#70-#73) mirror GitHub's own (#110-#114) — same subjects, same work. Cherry-picking them would have regressed quality.yml, which has since gained the enable-php switch, custom frontend checks and the report gate.

Verified by content rather than by commit subject:

GitHub Codeberg
quality.yml lines 2209 2091
omit=dev 5 4
audit 18 16

GitHub is a strict superset, so those four are already here.

Verification

  • quality.yml still 2209 lines after the port — not regressed
  • CONVENTIONS.md still present (Codeberg's branch lacks it; a blind overwrite would have deleted it)
  • All four cherry-picks applied without conflict

Found while auditing why a fix of mine went to Codeberg instead of GitHub — git remote -v | head -2 truncated the output and hid origin.

rubenvdlinde and others added 4 commits August 2, 2026 16:08
…stry, user AI-fluency, agent-platform maturity) (#74)
…eir real checkouts

These five were mounted from ../openregister/custom_apps/<app>, a stale second
copy: decidesk and openbuild are not git repositories there at all, petstore
points at nextcloud-app-template, and shillinq sat five patch versions behind
(0.9.18 vs 0.9.23). The container therefore ran code nobody was editing, which
silently invalidated every live verification done against those apps.

Also adds a planix mount — it had none, so nothing about planix could ever be
verified against this instance. Mounting does not enable it.

Applied to both the postgres 'nextcloud' service and 'nextcloud-mariadb'.
Compose derives its project name from the working directory, so running this
file from .github/ targets a project called 'github' rather than the
'openregister' project the live stack was created under. That project is not
empty -- other worktrees run CI-local stacks from their own .github/ dirs and
their containers carry project=github too.

A bare 'docker compose up -d --force-recreate nextcloud' from this directory
therefore resolved a procest CI container as its 'nextcloud' service and
stopped it, then failed on a name clash with conduction-postgres. Records the
correct invocation.
@rubenvdlinde
rubenvdlinde merged commit 678ecd2 into main Aug 2, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant