The local project had two remotes, origin (Gitea) and github. Gitea already pushes to GitHub through the push mirror, so a push to origin reaches GitHub and the second remote is not needed. It also invites a push that goes around the mirror. The script now adds origin only, with or without GitHub. The version is raised to 0.3.1.
An existing github remote, such as one made by an earlier version, is left as it is, and a different origin is still refused.
README.md: describes the one remote and git remote remove github for an old one
tests/test-local.sh: origin is the only remote with and without GitHub, no GitHub address in .git/config, an existing github remote is kept
src/lib/constants.sh and tests/test-security.sh: version 0.3.1
Docs: new MIL-008 and review record RC-031; Business Case objective 4, US-001.03, UC-001 step 8, OC-001 P9, SD-001, DCD-001, DCD-002, DM-001, DM-002, MIL-003, the project plan and the traceability matrix describe one remote
Review notes
Full test suite on the branch head: 1141 checks, 0 failed, 0 static checks failed.
S02 gave the Go on RC-031 and accepted MIL-008. The new Version History rows of the changed documents are Accepted and the rows before them Deprecated.
Plan: the plan was waived in chat for the remote fix. The plan-first gate refused that code commit (79f6ede) because MIL-008 was still Proposed, so it was made with ALLOW_UNPLANNED=1; it carries the Task: MIL-008#1 to #3 trailers. The version bump (538e44c) went through the gate normally with Task: MIL-008#4.
The tasks of MIL-008 are synced as milestone 78 and issues #59 to #62.
After the merge
Release v0.3.1 is tagged on Gitea from the merge commit on main (criterion 7 and task 4 of MIL-008).
The local project had two remotes, `origin` (Gitea) and `github`. Gitea already pushes to GitHub through the push mirror, so a push to `origin` reaches GitHub and the second remote is not needed. It also invites a push that goes around the mirror. The script now adds `origin` only, with or without GitHub. The version is raised to 0.3.1.
An existing `github` remote, such as one made by an earlier version, is left as it is, and a different `origin` is still refused.
## What changed
- `src/lib/localproject.sh`: `create_local_project` adds `origin` only; `src/lib/hosts.sh`: `github_remote_url` removed (nothing else used it)
- `README.md`: describes the one remote and `git remote remove github` for an old one
- `tests/test-local.sh`: `origin` is the only remote with and without GitHub, no GitHub address in `.git/config`, an existing `github` remote is kept
- `src/lib/constants.sh` and `tests/test-security.sh`: version 0.3.1
- Docs: new MIL-008 and review record RC-031; Business Case objective 4, US-001.03, UC-001 step 8, OC-001 P9, SD-001, DCD-001, DCD-002, DM-001, DM-002, MIL-003, the project plan and the traceability matrix describe one remote
## Review notes
- Full test suite on the branch head: 1141 checks, 0 failed, 0 static checks failed.
- S02 gave the Go on RC-031 and accepted MIL-008. The new Version History rows of the changed documents are `Accepted` and the rows before them `Deprecated`.
- Plan: the plan was waived in chat for the remote fix. The plan-first gate refused that code commit (`79f6ede`) because MIL-008 was still `Proposed`, so it was made with `ALLOW_UNPLANNED=1`; it carries the `Task: MIL-008#1` to `#3` trailers. The version bump (`538e44c`) went through the gate normally with `Task: MIL-008#4`.
- The tasks of MIL-008 are synced as milestone 78 and issues #59 to #62.
## After the merge
Release `v0.3.1` is tagged on Gitea from the merge commit on `main` (criterion 7 and task 4 of MIL-008).
Closes #59
Closes #60
Closes #61
Closes #62
A project created by the script had two remotes, origin (Gitea) and github.
Gitea already pushes to GitHub through the push mirror, so the second remote
is not needed and invites a push that goes around the mirror.
- MIL-008 and its review record RC-031
- Objective 4, US-001.03, UC-001 step 8, OC-001 P9, SD-001, DCD-001, DCD-002,
DM-001 and DM-002 describe one remote; MIL-003 criterion 1 and task 1 follow
- Project plan and traceability matrix list MIL-008 and RC-031
create_local_project no longer adds a github remote, with or without GitHub:
a push to origin reaches GitHub through the push mirror. A github remote that
already exists, such as one made by an earlier version, is left as it is, and
a different origin is still refused.
- Remove github_remote_url, which nothing else used
- README describes the one remote and how to remove an old github remote
- Tests: origin is the only remote with and without GitHub, no GitHub address
in .git/config, and an existing github remote is kept
Task: MIL-008#1
Task: MIL-008#2
Task: MIL-008#3
The version is raised to 0.3.1 and release v0.3.1 is tagged on Gitea from the
merge commit once the pull request is merged. MIL-008 gets task 4 and
criterion 7; RC-031 counts seven criteria.
- RC-031 is Accepted with a Go verdict and no open action items
- MIL-008 and the documents it changes are set to Accepted (previous rows
Deprecated): BC-001, US-001, UC-001, OC-001, SD-001, DCD-001, DCD-002,
DM-001, DM-002, MIL-003, PP-001 and TM-001
Tirsvad
changed title from Gitea is the only remote: plan MIL-008 and add only origin to the local project to Gitea is the only remote (MIL-008) and version 0.3.12026-10-08 05:43:14 +02:00
Tirsvad
merged commit b90050e6c4 into main2026-10-08 05:45:00 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The local project had two remotes,
origin(Gitea) andgithub. Gitea already pushes to GitHub through the push mirror, so a push tooriginreaches GitHub and the second remote is not needed. It also invites a push that goes around the mirror. The script now addsoriginonly, with or without GitHub. The version is raised to 0.3.1.An existing
githubremote, such as one made by an earlier version, is left as it is, and a differentoriginis still refused.What changed
src/lib/localproject.sh:create_local_projectaddsoriginonly;src/lib/hosts.sh:github_remote_urlremoved (nothing else used it)README.md: describes the one remote andgit remote remove githubfor an old onetests/test-local.sh:originis the only remote with and without GitHub, no GitHub address in.git/config, an existinggithubremote is keptsrc/lib/constants.shandtests/test-security.sh: version 0.3.1Review notes
Acceptedand the rows before themDeprecated.79f6ede) because MIL-008 was stillProposed, so it was made withALLOW_UNPLANNED=1; it carries theTask: MIL-008#1to#3trailers. The version bump (538e44c) went through the gate normally withTask: MIL-008#4.After the merge
Release
v0.3.1is tagged on Gitea from the merge commit onmain(criterion 7 and task 4 of MIL-008).Closes #59
Closes #60
Closes #61
Closes #62
Gitea is the only remote: plan MIL-008 and add only origin to the local projectto Gitea is the only remote (MIL-008) and version 0.3.1