Clarify the public org profile: toolchain first, archived Next.js named - #1
Merged
Merged
Conversation
Rewrite the public GitHub org README so visitors see the active toolchain first, and so star-sorted Next.js history is labeled as archived rather than implied. Co-authored-by: Damon Blais <damon@rethunk.tech>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved issues block approval.
Pull request overview
Updates the public organization profile to foreground active developer tooling and distinguish archived repositories from related Rethunk-AI work.
Changes:
- Refines organization and product positioning.
- Updates active repository descriptions.
- Lists archived repositories and links the OSS directory.
File summaries
| File | Description |
|---|---|
profile/README.md |
Updates public profile messaging, repository listings, archived repositories, and related links. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This branch was successfully deployed
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.
This updates what visitors see on github.com/Rethunk-Tech.
GitHub’s org landing page still ranks public repos by stars, so archived Next.js work (
nextjs-boilerplate,next-ui-builder) appears first. The profile README (profile/README.md) is the in-repo copy we control. Pins are not managed from this file, so this PR does not claim pinned-repo control.Intent
oss@rethunk.tech.What changed
Single file:
profile/README.md.heft,rethunk-git-cli,rethunk-gate-cli,claude-format-hooks,gh-actions.nextjs-boilerplate,next-ui-builder,wiki2go,TraceTrim,claude-plugins.Root
README.mdleft alone (it still says “pinned repositories”; that line is internal dossier copy, not the public org profile).Do not merge until reviewed.