Repository navigation
docs: drop moved renderer link and mark repository as hand-edited - #1
Merged
Merged
Conversation
The organization profile listed atrinik/renderer, which moved out of the organization in October and now redirects to another organization. Remove that row; every other linked repository is still in atrinik. The README said these files are generated from atrinik/github-settings and must not be edited directly. That generator was retired on 2026-11-14, so say instead that the repository is edited by hand through pull requests. Co-Authored-By: Claude <noreply@anthropic.com>
Dependency Review✅ No vulnerabilities or license issues found.Scanned FilesNone |
Member
Author
Self-reviewReviewed: the whole diff of this pull request (
The head commit has not changed since round 0. All fixes were PR-body edits only; there are no fix commits. Coverage limit: the PR-body edits made to handle the round-1 findings (the corrected profile-paragraph bullet and the rewritten ordering-dependency bullet) were not covered by a further review round that found nothing. The commit content itself was reviewed twice with no finding against the files. Findings
|
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
Fixes the public Atrinik organization profile and stops describing this repository as generated.
profile/README.md: removes therendererrow from the project table.atrinik/renderermoved out of the organization in October;gh api repos/atrinik/renderernow resolves toseraphinastudios/tilewright-renderer.README.md: the note said these files are generated fromatrinik/github-settingsand must not be edited directly. That generator was retired on 2026-11-14, so the note now says the repository is edited by hand through pull requests.Intent brief
atrinikorganization, and the README no longer tells people (or agents) to edit a retired generator instead of this repository.atrinik/editor, which also moved, is not linked anywhere in this repository, so nothing else needed changing. The word "editor" in theclassicrow describes Classic's own editor.atrinik/github-settingsin the note so readers who remember the old flow know it no longer applies.CONTRIBUTING.md,SECURITY.md,CODE_OF_CONDUCT.mdand the dependency-review workflow are untouched.Implementation / behavior
Two Markdown edits, one commit. None of the files carried a "generated" header comment; the only generated-file note was the README paragraph.
Validation
github.com/atrinik/NAMElink in the repository resolved withgh api repos/atrinik/NAME. All are inatrinikexceptrenderer, which redirects toseraphinastudios/tilewright-rendererand was removed.atrinik/atrinik#168(open) andatrinik/atrinik/docs/PROVENANCE.mdexist;https://atrinik.org/,https://atrinik.org/downloads/andhttps://zoeysr.comreturn 200.Limitations / follow-up
atrinik/github-settings(main) still describes this repository as a generated target that must never be hand-edited (AGENTS.md) and still shipsbin/publish-community-healthwith itscommunity-health/source, which the owner's login can still run. The installedatrinik-developmentskills (for exampleatrinik-github-governance) also still tell agents to "run the publisher plan before--apply". Both step-1 pull requests are the dependency: thegithub-settingstooling-removal PR (removes the publisher andcommunity-health/, correctsAGENTS.md) and theatrinik-developmentskill-correction PR (stops telling agents to run the publisher). Until both merge, an--applyrun of the publisher would overwrite this repository and restore the old "do not edit" note. Merging this pull request first is safe as long as nobody runs the publisher in the meantime; nothing here depends on those PRs otherwise.community-health/: the publisher copy is newer than this repository, not older.community-health/profile/README.mdongithub-settingsmain carries the closing paragraph the owner merged in docs(profile): describe creator tools as current practice github-settings#100 on 2026-10-18 ("Atrinik's creators shape the game world with whatever tools serve the work, including AI tools; …"), and it already has no renderer row (#99). This repository was last synced on 2026-10-12 (d520570), so it still shows the superseded "Human creators direct the game world" paragraph, which this pull request keeps unchanged because its scope is links and the generated-file note. That paragraph is the only content difference between the two copies. Follow-up: carry the #100 paragraph over in a separate pull request to this repository before the step-1 tooling-removal PR deletescommunity-health/, so the approved wording does not survive only in git history.atrinik/rendereris an owner-only action tracked elsewhere.🤖 Generated with Claude Code