Skip to content

Commit b91a950

Browse files
NagyViktNagyVikt
andauthored
Point public frontend links at the canonical frontend mirror (#219)
GitGuardex still exposed the old frontend mirror target in README instructions, workflow defaults, and package metadata. This aligns those surfaces with recodeee/gitguardex-frontend so the public repo metadata and the mirror automation point at the same destination. Constraint: User requested the repo surface link the frontend through recodeee/gitguardex-frontend Rejected: Keep homepage on guardextutorial.com while only changing docs | would leave public metadata inconsistent with the requested frontend link Confidence: high Scope-risk: narrow Directive: When the frontend mirror target changes again, update package metadata, README setup notes, and workflow defaults together Tested: node --test test/metadata.test.js Tested: openspec validate agent-codex-point-frontend-links-at-recodeee-fronten-2026-04-21-12-45 --type change --strict Not-tested: Live sync-frontend-mirror workflow run against the new target repo Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
1 parent 86a4718 commit b91a950

7 files changed

Lines changed: 26 additions & 6 deletions

File tree

.github/workflows/sync-frontend-mirror.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ jobs:
2121
sync:
2222
runs-on: ubuntu-latest
2323
env:
24-
TARGET_REPO: ${{ vars.GUARDEX_FRONTEND_MIRROR_REPO || 'Webu-PRO/guardex-frontend' }}
24+
TARGET_REPO: ${{ vars.GUARDEX_FRONTEND_MIRROR_REPO || 'recodeee/gitguardex-frontend' }}
2525
TARGET_BRANCH: ${{ vars.GUARDEX_FRONTEND_MIRROR_BRANCH || 'main' }}
2626
SOURCE_PREFIX: frontend
2727
SYNC_TOKEN: ${{ secrets.GUARDEX_FRONTEND_MIRROR_PAT }}

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -462,17 +462,17 @@ If `package.json` exists, setup also adds `agent:*` helper scripts.
462462

463463
## Frontend mirror
464464

465-
- Standalone frontend repo: <https://github.com/Webu-PRO/guardex-frontend>
465+
- Standalone frontend repo: <https://github.com/recodeee/gitguardex-frontend>
466466
- This repo tracks the frontend under `frontend/` and auto-mirrors it via `.github/workflows/sync-frontend-mirror.yml` on changes to `main`.
467467

468468
Setup (in this repo):
469469

470470
1. `Settings → Secrets and variables → Actions`
471-
2. Add secret `GUARDEX_FRONTEND_MIRROR_PAT` with `contents:write` on `Webu-PRO/guardex-frontend`
471+
2. Add secret `GUARDEX_FRONTEND_MIRROR_PAT` with `contents:write` on `recodeee/gitguardex-frontend`
472472

473473
Optional overrides (Actions Variables):
474474

475-
- `GUARDEX_FRONTEND_MIRROR_REPO` (default `Webu-PRO/guardex-frontend`)
475+
- `GUARDEX_FRONTEND_MIRROR_REPO` (default `recodeee/gitguardex-frontend`)
476476
- `GUARDEX_FRONTEND_MIRROR_BRANCH` (default `main`)
477477

478478
Manual run:
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
schema: spec-driven
2+
created: 2026-04-21
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# T1 Notes
2+
3+
- Handoff: own `README.md`, `package.json`, `.github/workflows/sync-frontend-mirror.yml`, and `test/metadata.test.js` to point GitGuardex at `recodeee/gitguardex-frontend` instead of the old frontend target.
4+
- Change the public homepage metadata to the new frontend repo link so the repo surface and package metadata stay aligned.
5+
- Keep README mirror instructions and workflow defaults consistent with the new mirror destination.
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
## ADDED Requirements
2+
3+
### Requirement: Canonical frontend mirror links stay aligned
4+
GitGuardex MUST expose `https://github.com/recodeee/gitguardex-frontend` as the canonical standalone frontend repo across public metadata and default mirror configuration.
5+
6+
#### Scenario: Public metadata points at the canonical frontend repo
7+
- **WHEN** maintainers inspect `package.json` homepage metadata or the README frontend mirror section
8+
- **THEN** they see `https://github.com/recodeee/gitguardex-frontend`
9+
- **AND** the older `Webu-PRO/guardex-frontend` target is not presented as the default frontend repo
10+
11+
#### Scenario: Mirror workflow defaults to the canonical frontend repo
12+
- **WHEN** `.github/workflows/sync-frontend-mirror.yml` runs without `GUARDEX_FRONTEND_MIRROR_REPO`
13+
- **THEN** the workflow defaults `TARGET_REPO` to `recodeee/gitguardex-frontend`

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@
6060
"bugs": {
6161
"url": "https://github.com/recodeee/gitguardex/issues"
6262
},
63-
"homepage": "https://guardextutorial.com",
63+
"homepage": "https://github.com/recodeee/gitguardex-frontend",
6464
"funding": "https://github.com/sponsors/recodeecom",
6565
"publishConfig": {
6666
"access": "public"

test/metadata.test.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ test('package manifest includes repository and support metadata', () => {
1616

1717
assert.equal(pkg.repository?.url, 'git+https://github.com/recodeee/gitguardex.git');
1818
assert.equal(pkg.bugs?.url, 'https://github.com/recodeee/gitguardex/issues');
19-
assert.equal(pkg.homepage, 'https://guardextutorial.com');
19+
assert.equal(pkg.homepage, 'https://github.com/recodeee/gitguardex-frontend');
2020
assert.equal(pkg.publishConfig?.access, 'public');
2121
});
2222

0 commit comments

Comments
 (0)