docs: canonical URL is https://jonbogaty.com/pkgs/#7
Conversation
The operator's apex jonbogaty.com already CNAMEs to jbcom.github.io repo-wide, so GitHub Pages transparently serves /pkgs/ on the apex with no reverse proxy needed. Updates astro.config.mjs `site` field to feed correct absolute URLs into sitemap + OG tags, and aligns README / CLAUDE.md / AGENTS.md / docs/ to the real canonical URL. jbcom.github.io/pkgs/ 301-redirects to the canonical URL.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 47 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR cleanly updates documentation and configuration to reflect the canonical URL change from jbcom.github.io/pkgs to jonbogaty.com/pkgs. The changes are consistent across all files, and the Astro configuration correctly uses site: "https://jonbogaty.com" with base: "/pkgs" for the subpath deployment. The documentation properly explains the CNAME setup and includes important warnings about not adding a public/CNAME file. No blocking issues identified.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
There was a problem hiding this comment.
Pull request overview
Updates the repo’s canonical/public URL from the GitHub Pages subdomain to the apex-domain subpath (https://jonbogaty.com/pkgs/) and removes now-stale reverse-proxy guidance, aligning docs/config with the current GitHub Pages custom-domain routing setup.
Changes:
- Update Astro
siteconfig to usehttps://jonbogaty.comfor correct absolute URLs (sitemap/OG) while keepingbase: /pkgs. - Update deployment + architecture docs and README to reference
https://jonbogaty.com/pkgs/. - Remove “reverse-proxy pending” notes from docs.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/STATE.md | Removes reverse-proxy pending note. |
| docs/DEPLOYMENT.md | Updates production URL + DNS/custom-domain guidance to reflect apex routing. |
| docs/ARCHITECTURE.md | Updates architecture explanation for serving at jonbogaty.com/pkgs/. |
| astro.config.mjs | Sets site to https://jonbogaty.com (keeping base: /pkgs). |
| README.md | Updates public site URL references. |
| CLAUDE.md | Updates public site URL references. |
| The operator's apex domain `jonbogaty.com` already CNAMEs to | ||
| `jbcom.github.io`, so GitHub Pages transparently serves `/pkgs/` at | ||
| `https://jonbogaty.com/pkgs/`. `jbcom.github.io/pkgs/` 301-redirects | ||
| to the canonical URL. |
There was a problem hiding this comment.
“The operator's apex domain jonbogaty.com already CNAMEs to jbcom.github.io” is DNS-inaccurate for an apex/root record (it usually can’t be a literal CNAME). Reword to something like “is configured to resolve to / point at jbcom.github.io” to avoid implying an invalid DNS record type.
| The operator's apex domain `jonbogaty.com` already CNAMEs to | |
| `jbcom.github.io`, so GitHub Pages transparently serves `/pkgs/` at | |
| `https://jonbogaty.com/pkgs/`. `jbcom.github.io/pkgs/` 301-redirects | |
| to the canonical URL. | |
| The operator's apex domain `jonbogaty.com` is already configured to | |
| point at `jbcom.github.io`, so GitHub Pages transparently serves | |
| `/pkgs/` at `https://jonbogaty.com/pkgs/`. `jbcom.github.io/pkgs/` | |
| 301-redirects to the canonical URL. |
| @@ -142,7 +142,7 @@ PY | |||
|
|
|||
| `deploy.yml` runs on every push to `main` using `withastro/action@v6`. | |||
There was a problem hiding this comment.
This references deploy.yml, but the repo’s Pages workflow file is .github/workflows/cd.yml. Updating this (and any other mentions in the README) will keep the docs consistent with the actual workflow name.
| `deploy.yml` runs on every push to `main` using `withastro/action@v6`. | |
| `.github/workflows/cd.yml` runs on every push to `main` using `withastro/action@v6`. |
|
|
||
| Currently served on the GitHub-issued subdomain | ||
| (`jbcom.github.io/pkgs`). To serve `jonbogaty.com/pkgs` in the future: | ||
| The operator's apex `jonbogaty.com` already CNAMEs to |
There was a problem hiding this comment.
The phrase “apex jonbogaty.com already CNAMEs to jbcom.github.io” is DNS-inaccurate: apex/root records generally can’t be a CNAME (some providers offer ALIAS/ANAME flattening). Consider rewording to “resolves to / points at jbcom.github.io” so operators don’t copy an invalid DNS setup.
| The operator's apex `jonbogaty.com` already CNAMEs to | |
| The operator's apex `jonbogaty.com` already resolves to |
Updates site config + docs to reflect that jonbogaty.com CNAMEs to jbcom.github.io repo-wide, so GitHub Pages transparently serves /pkgs/ at the apex. No reverse-proxy setup needed after all.
Verified live: https://jonbogaty.com/pkgs/ serves the built site.