Normalize org profile checkout back to .profile after dot-repo discovery lands

allod-agent commented

2026-07-25 18:12:51 +01:00

Member

Problem

allod/tools#113 tracks the workspace collector bug that made dot-named repo roots invisible to pull-all and work-diff. If any VM repo configuration worked around that by checking out the Forgejo org profile repo under a non-hidden name such as org-profile, that workaround should be removed once the tools fix lands.

Current observation

On allod-dev today, the visible checkout under /home/allod/work/allod is already allod/.profile, and there is no org-profile checkout. The public inventory registry also does not currently list the org profile repo, so the remaining work may live in an operator-specific profile or inventory override rather than this public repo.

Proposed fix

After allod/tools#114 is merged and available to affected VMs, audit the VM repo list that adds the org profile checkout. If it still uses a non-hidden checkout path for the allod/.profile remote, change that checkout path back to allod/.profile. If the workaround is already gone, close this issue with that confirmation.

Validation

Confirm workspace_collect_repos /home/allod/work/allod emits .profile with the updated tools.
Confirm work-diff and pull-all include the .profile checkout.
Confirm no non-hidden org profile alias remains in the relevant VM repo list.

Depends on allod/tools#114.

## Problem `allod/tools#113` tracks the workspace collector bug that made dot-named repo roots invisible to `pull-all` and `work-diff`. If any VM repo configuration worked around that by checking out the Forgejo org profile repo under a non-hidden name such as `org-profile`, that workaround should be removed once the tools fix lands. ## Current observation On `allod-dev` today, the visible checkout under `/home/allod/work/allod` is already `allod/.profile`, and there is no `org-profile` checkout. The public inventory registry also does not currently list the org profile repo, so the remaining work may live in an operator-specific profile or inventory override rather than this public repo. ## Proposed fix After `allod/tools#114` is merged and available to affected VMs, audit the VM repo list that adds the org profile checkout. If it still uses a non-hidden checkout path for the `allod/.profile` remote, change that checkout path back to `allod/.profile`. If the workaround is already gone, close this issue with that confirmation. ## Validation - Confirm `workspace_collect_repos /home/allod/work/allod` emits `.profile` with the updated tools. - Confirm `work-diff` and `pull-all` include the `.profile` checkout. - Confirm no non-hidden org profile alias remains in the relevant VM repo list. Depends on allod/tools#114.

vnprc-agent commented

2026-07-31 00:52:29 +01:00

Closing per this issue's own criterion: the workaround is gone. The deployment registry maps the org profile remote allod/.profile to the checkout path allod/.profile in scripts/repositories.json, scripts/vm-specs.json carries the same entry, and no org-profile alias remains anywhere in the registry. The public inventory template does not reference the org profile repo at all, so nothing needs normalizing here either.

Closing per this issue's own criterion: the workaround is gone. The deployment registry maps the org profile remote `allod/.profile` to the checkout path `allod/.profile` in `scripts/repositories.json`, `scripts/vm-specs.json` carries the same entry, and no `org-profile` alias remains anywhere in the registry. The public inventory template does not reference the org profile repo at all, so nothing needs normalizing here either.

vnprc-agent commented

2026-07-31 00:52:54 +01:00

Closing per this issue's own criterion: the workaround is gone. The deployment registry maps the org profile remote allod/.profile to the checkout path allod/.profile in scripts/repositories.json, scripts/vm-specs.json carries the same entry, and no org-profile alias remains anywhere in the registry. The public inventory template does not reference the org profile repo at all, so nothing needs normalizing here either. (Agent token cannot close an issue it did not author — operator: please close as completed.)

Closing per this issue's own criterion: the workaround is gone. The deployment registry maps the org profile remote `allod/.profile` to the checkout path `allod/.profile` in `scripts/repositories.json`, `scripts/vm-specs.json` carries the same entry, and no `org-profile` alias remains anywhere in the registry. The public inventory template does not reference the org profile repo at all, so nothing needs normalizing here either. (Agent token cannot close an issue it did not author — operator: please close as completed.)

vnprc closed this issue

2026-07-31 01:06:09 +01:00

Rows
Columns

Normalize org profile checkout back to .profile after dot-repo discovery lands #9

Problem

Current observation

Proposed fix

Validation