Repository navigation
chore: finish the Guard-Core org migration (docs, metadata, links) - #28
Merged
Merged
Conversation
Point every docs, metadata and cross-reference URL at the Guard-Core org and the guard-core.github.io Pages host, keep the mkdocs author profile personal, leave CHANGELOG and release-notes history untouched, and fix the llms.txt Contributing link that pointed at blob/main.
Contributor
|
Thanks for opening your first pull request on djangoapi-guard! Quick checklist before review (most of these are enforced by CI, but worth a glance):
See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow. Welcome aboard — a maintainer will review shortly. |
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.
Summary
Finishes the Guard-Core org migration for everything the workflow/OIDC pass (#27) did not cover: documentation, repo metadata, cross-references, and packaging URLs. History entries are intentionally preserved.
Categories of changes
rennf93.github.io/djapi-guard->guard-core.github.io/djapi-guard(path suffixes preserved) in README, mkdocs.yml (site_url, og:image), pyproject Documentation URL, issue template, SECURITY.md, docs/index.md, docs/llms.txt, docs/robots.txtgithub.com/rennf93/->github.com/Guard-Core/across README (hero, badges, ecosystem tables, acknowledgements), mkdocs.yml (repo_name, repo_url, social, feedback), pyproject project.urls, SECURITY.md, issue template, docs pages, AGENTS.md, CLAUDE.md, SKILL.md, llms.txtghcr.io/rennf93/->ghcr.io/guard-core/in docs/index.md pull examples and thebump_version.pyregex so future bumps keep matchingGuard-Coregithub.com/orgs/Guard-Core/...rennf93@guard-core.com; README author contact and CODE_OF_CONDUCT contact ->contact@guard-core.comgithub: rennf93->github: Guard-Core(tidelift and paypal lines kept)blob/main, repo default branch ismasterIntentionally untouched
.github/workflows/docs.ymland.github/workflows/release.ymluses:references torennf93/github-actions-secrets-mgmtandrennf93/upsert-context7: those action repositories do not exist under Guard-Core yet (404), so repointing them here would break the docs deploy and release pipelinesVerification
uv run ruff format --check+uv run ruff checkon touched Python: cleanuv run mypy .: 45 pre-existing errors in tests/, byte-identical to the base commit, 0 new; touchedbump_version.pyclean on its ownuv run mkdocs build --strict: exit 0, output identical to base, no new errorsuv run pymarkdownlnt scan: findings identical to base (all inside .venv site-packages), 0 newpyproject.tomlparses viatomllibon 3.12, urls and author email verifiedgit grep -n rennf93after edits: 11 lines, down from 167rennf93@guard-core.com, correct as-isuses:action refs, blocked on the action repos joining the org