Repository navigation
chore: untrack .wrangler cache, add sitemap.xml and robots.txt - #13
Merged
Merged
Conversation
- Stop tracking .wrangler/ (local Wrangler cache with Cloudflare account/project metadata) and ignore it - Add website/sitemap.xml for index, privacy, terms, refunds - Add website/robots.txt pointing to the sitemap
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
.wrangler/from git tracking (git rm -r --cached) and adds it to.gitignore. These are local Wrangler CLI cache files.website/sitemap.xml(/, /privacy, /terms, /refunds) andwebsite/robots.txtreferencing it.Deployment
The site appears to be deployed to Cloudflare Pages from
website/(the.wrangler/cache/pages.jsonproject cache;index.htmlsits at the root ofwebsite/), so both new files should be served at https://superpaste.ai/sitemap.xml and /robots.txt. Verify after the next deploy.Security note
The removed files remain in git history. I checked them: they contain Cloudflare account ID/name and Pages project name only, with no API tokens or secrets. An account ID isn't a credential, so rotation shouldn't be required. If any Cloudflare token has ever been committed elsewhere, rotate it, since history keeps it.
Do not merge without review.