d-bis/proxmox
4
0
Fork 0
Code Issues 2 Pull Requests 13 Actions Packages Projects Releases Wiki Activity

chore(submodules): Phase 3 — move 4 SSH-URL submodules to HTTPS #2

Open
nsatoshi wants to merge 1 commits from devin/phase3-submodule-remotes-1776542381 into master
pull from: devin/phase3-submodule-remotes-1776542381
merge into: d-bis:master
Conversation 0 Commits 1 Files Changed 2 +62 -7
nsatoshi commented 2026-04-18 20:02:51 +00:00
Owner
Copy Link

Summary

Part of the sequenced cleanup tracked in issue #1. Phase 3 — remote-URL fixes for submodules whose .gitmodules URL is git@github.com:… SSH, which fails git submodule update --init in HTTPS-only environments.

Submodule Before After Why that remote
smom-dbis-138 git@github.com:Order-of-Hospitallers/smom-dbis-138.git https://gitea.d-bis.org/d-bis/smom-dbis-138.git Pinned commit 07d9ce48 only on Gitea; canonical per AGENTS.md.
metamask-integration git@github.com:Defi-Oracle-Meta-Blockchain/metamask-integration.git https://gitea.d-bis.org/d-bis/metamask-integration.git Reachable both; prefer Gitea per AGENTS.md.
dbis_core git@github.com:Order-of-Hospitallers/dbis_core.git https://github.com/Order-of-Hospitallers/dbis_core.git Pinned commit only on GitHub; Gitea mirror lags.
the-order git@github.com:Order-of-Hospitallers/the-order-monorepo.git https://github.com/Order-of-Hospitallers/the-order-monorepo.git No Gitea mirror of the-order-monorepo.

No submodule pointers change — only remote URLs. Each updated URL was verified by a clean git submodule update --init <name> from a .git-less directory. docs/00-meta/SUBMODULE_HYGIENE.md gets a remote-status matrix and follow-up list.

Review & Testing Checklist for Human

Risk: yellow — no code change, but .gitmodules edits can break every downstream clone if a URL is wrong.

  • From a fresh checkout of this branch, git submodule sync && git submodule update --init --recursive succeeds without auth prompts or 403s for all 4 touched submodules.
  • git submodule status smom-dbis-138 metamask-integration dbis_core the-order on this branch reports the same 4 pinned SHAs as master (no pointer drift).
  • CI workflows that do a submodule checkout still pass.

Notes

Follow-up items tracked in docs/00-meta/SUBMODULE_HYGIENE.md:

  1. Migrate dbis_core to Gitea once the mirror catches up.
  2. Decide whether to host a Gitea mirror for the-order-monorepo.
  3. Remove / convert omada-api (403 from HTTPS-only envs).
  4. Review pr-workspace/app-ethereum and pr-workspace/chains (personal defiQUG/ forks).

Tracking: issue #1 — this PR is the remote-URL subset only, no secret rotation.

## Summary Part of the sequenced cleanup tracked in issue #1. Phase 3 — remote-URL fixes for submodules whose `.gitmodules` URL is `git@github.com:…` SSH, which fails `git submodule update --init` in HTTPS-only environments. | Submodule | Before | After | Why that remote | |---|---|---|---| | `smom-dbis-138` | `git@github.com:Order-of-Hospitallers/smom-dbis-138.git` | `https://gitea.d-bis.org/d-bis/smom-dbis-138.git` | Pinned commit `07d9ce48` only on Gitea; canonical per AGENTS.md. | | `metamask-integration` | `git@github.com:Defi-Oracle-Meta-Blockchain/metamask-integration.git` | `https://gitea.d-bis.org/d-bis/metamask-integration.git` | Reachable both; prefer Gitea per AGENTS.md. | | `dbis_core` | `git@github.com:Order-of-Hospitallers/dbis_core.git` | `https://github.com/Order-of-Hospitallers/dbis_core.git` | Pinned commit only on GitHub; Gitea mirror lags. | | `the-order` | `git@github.com:Order-of-Hospitallers/the-order-monorepo.git` | `https://github.com/Order-of-Hospitallers/the-order-monorepo.git` | No Gitea mirror of `the-order-monorepo`. | No submodule **pointers** change — only remote URLs. Each updated URL was verified by a clean `git submodule update --init <name>` from a `.git`-less directory. `docs/00-meta/SUBMODULE_HYGIENE.md` gets a remote-status matrix and follow-up list. ## Review & Testing Checklist for Human Risk: **yellow** — no code change, but `.gitmodules` edits can break every downstream clone if a URL is wrong. - [ ] From a fresh checkout of this branch, `git submodule sync && git submodule update --init --recursive` succeeds without auth prompts or 403s for all 4 touched submodules. - [ ] `git submodule status smom-dbis-138 metamask-integration dbis_core the-order` on this branch reports the same 4 pinned SHAs as `master` (no pointer drift). - [ ] CI workflows that do a submodule checkout still pass. ### Notes Follow-up items tracked in `docs/00-meta/SUBMODULE_HYGIENE.md`: 1. Migrate `dbis_core` to Gitea once the mirror catches up. 2. Decide whether to host a Gitea mirror for `the-order-monorepo`. 3. Remove / convert `omada-api` (403 from HTTPS-only envs). 4. Review `pr-workspace/app-ethereum` and `pr-workspace/chains` (personal `defiQUG/` forks). Tracking: issue #1 — this PR is the remote-URL subset only, no secret rotation.
nsatoshi added 1 commit 2026-04-18 20:02:52 +00:00
chore(submodules): move 4 SSH-URL submodules to HTTPS (Phase 3)
Some checks failed
AI Code Review / claude-review (pull_request) Failing after 2m10s
Details
25283c3eaf 
Switch smom-dbis-138, metamask-integration, dbis_core, the-order from
git@github.com: SSH URLs to https:// URLs so git submodule update --init
works in HTTPS-only environments (CI containers, Devin agents, etc.).

Per AGENTS.md, the canonical source is Gitea, so prefer gitea.d-bis.org
where the currently-pinned commit is actually reachable:

- smom-dbis-138      -> gitea.d-bis.org/d-bis/smom-dbis-138      (Gitea only)
- metamask-integration -> gitea.d-bis.org/d-bis/metamask-integration (Gitea + GitHub)
- dbis_core          -> github.com/Order-of-Hospitallers/dbis_core (GitHub only; Gitea mirror lags)
- the-order          -> github.com/Order-of-Hospitallers/the-order-monorepo (no Gitea mirror)

Reachability of each pinned commit verified 2026-04-18 via git ls-remote
and shallow fetch. Documented the full remote-status matrix and follow-up
migration candidates (dbis_core, the-order, omada-api, pr-workspace/*) in
docs/00-meta/SUBMODULE_HYGIENE.md.

No submodule pointers changed; this is remote-URL-only.

Tracking: #1
Co-Authored-By: Nakamoto, S <defi@defi-oracle.io>
Some checks failed
AI Code Review / claude-review (pull_request) Failing after 2m10s
Details
Checking for merge conflicts…
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin devin/phase3-submodule-remotes-1776542381:devin/phase3-submodule-remotes-1776542381
git checkout devin/phase3-submodule-remotes-1776542381
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
70rn4710n A.r.yavari SEG nsatoshi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: d-bis/proxmox#2
Delete Branch "devin/phase3-submodule-remotes-1776542381"

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?