You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4f991e0
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Registry Stack Marketplace
2
2
3
3
Separate Astro static marketplace for marketplace.registrystack.org.
4
-
PR preview deployment is authorized. Production deployment stays disabled until Jeremi explicitly authorizes it.
4
+
Regular GitHub Pages deployment is authorized. Resolve the repository visibility or plan prerequisite before enabling PAGES_DEPLOYMENT_ENABLED. Never change repository visibility without Jeremi’s explicit approval.
5
5
6
6
- npm run check:ci validates a clean checkout without private assets.
7
7
- npm run check adds explicit local private-archive verification.
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Registry Stack Marketplace
2
2
3
-
Astro static site for marketplace.registrystack.org, kept local and unpublished for review. The source lives in the private registrystack/marketplace repository. Production hosting, domain changes, and production deployment remain disabled.
3
+
Astro static site for marketplace.registrystack.org, kept local and unpublished for review. The source lives in the private registrystack/marketplace repository. Regular GitHub Pages deployment is prepared, with activation pending the repository visibility or plan prerequisite.
4
4
5
5
## Review locally
6
6
@@ -75,7 +75,7 @@ For compatibility with the existing native request form, requests use request_ty
75
75
76
76
## Repository and CI
77
77
78
-
The repository is private at https://github.com/registrystack/marketplace. Marketplace CI runs on pull requests, pushes to main, and manual dispatch. Its token is read-only; it has no production deployment job, Pages write permission, production domain binding, or production secret configuration. Official actions are pinned to immutable commits.
78
+
The repository is private at https://github.com/registrystack/marketplace. Marketplace CI runs on pull requests, pushes to main, and manual dispatch. Its build token is read-only. A separate Pages deployment job has the Pages and OIDC permissions required for publication; it runs only after successful checks on main and when PAGES_DEPLOYMENT_ENABLED is exactly true. Official actions are pinned to immutable commits.
79
79
80
80
The workflow installs locked dependencies, runs check:ci, executes browser journeys on a temporary loopback server, and checks the fully intercepted request/analytics funnel. It uploads only the verified dist/ site and browser review images, retained for seven days. Preview output rejects ZIPs and other archives, private asset paths, live request/analytics configuration, and indexable HTML.
81
81
@@ -85,4 +85,4 @@ The tracking protocol and shared client are pinned by data/tracking-contract.jso
85
85
86
86
Those pins describe the prepared protocol-v3 integration. They do not claim that the main website and documentation have been deployed with it.
87
87
88
-
PR preview hosting is configured separately from these CI artifacts. A built artifact is not a deployed preview URL. Production remains disabled while the preview hosting account is selected and connected.
88
+
The selected host is regular GitHub Pages. Pull requests produce CI review artifacts; main can publish the checked Pages artifact after explicit activation. GitHub currently refuses Pages activation for this private repository on the organization plan. See docs/github-pages.md for activation steps and the Cloudflare DNS configuration. No separate PR hosting service is required.
The marketplace uses the regular GitHub Pages deployment from the checked main branch. CI still runs on every pull request. It publishes only after checks pass, from main, and when the repository variable PAGES_DEPLOYMENT_ENABLED is exactly true. Pull requests never deploy to the production Pages environment.
4
+
5
+
## Current activation prerequisite
6
+
7
+
The repository was created private. GitHub rejected Pages activation because the current organization plan does not support Pages for this private repository. The repository must either become public with the owner's explicit approval, or the organization must use a GitHub plan that supports private-repository Pages. Changing source visibility and changing website visibility are different actions; a public website does not require its source to be public on a suitable plan.
8
+
9
+
No private archive bytes are tracked or uploaded. The 87 request-only ZIPs remain in ignored content/downloads/. Only static catalogue pages, CSS, and browser scripts enter the checked deployment artifact.
10
+
11
+
## DNS configuration
12
+
13
+
In the registrystack.org Cloudflare zone:
14
+
15
+
| Setting | Value |
16
+
| --- | --- |
17
+
| Type | CNAME |
18
+
| Name | marketplace |
19
+
| Target | registrystack.github.io |
20
+
| Proxy status | DNS only, grey cloud |
21
+
| TTL | Auto |
22
+
23
+
The equivalent Cloudflare API request body is in [cloudflare-dns.json](cloudflare-dns.json). TTL 1 represents Auto. The CNAME target is the organization hostname, without a repository path.
24
+
25
+
Because this record is DNS only, GitHub serves the TLS certificate. Cloudflare's proxy SSL mode does not control this hostname.
26
+
27
+
## GitHub activation
28
+
29
+
After resolving the repository plan or visibility prerequisite:
30
+
31
+
1. In repository Settings, Pages, select GitHub Actions as the deployment source.
32
+
2. Set the custom domain to marketplace.registrystack.org. A CNAME file in this repository is not required by the Actions publishing method.
33
+
3. Confirm DNS points to registrystack.github.io and enable Enforce HTTPS when GitHub has issued the certificate. Certificate provisioning can take up to 24 hours.
34
+
4. Set the repository variable PAGES_DEPLOYMENT_ENABLED to true.
35
+
5. Run Marketplace CI on main, or push a main-branch change. The deploy job consumes the same artifact that passed the checks.
36
+
37
+
Setting the activation variable to any other value disables publication. GitHub Pages must be enabled first; the flag does not bypass a GitHub plan restriction.
38
+
39
+
The initial deployment retains noindex metadata and disallow-all robots.txt while the content remains under review. Form submissions and analytics remain unconfigured. Removing those review controls and enabling live integrations require a deliberate subsequent change.
for(constcheckof['npm ci','npm run check:ci','node scripts/check-browser.mjs','npm run test:funnel','node scripts/verify-preview-artifact.mjs'])assert.ok(workflow.includes(check),check);
0 commit comments