feat(docs): migrate RFC process back to main repository #15242
Conversation
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
Migrate the RFC (Request for Comments) process from the separate datahub-project/rfcs repository back to the main DataHub repository to improve visibility and reduce contributor friction. This represents a "fresh start" for RFCs - historical RFCs remain accessible in git history and the archived external repository, but will be migrated on an as-needed basis when they become relevant. Changes: - Created docs/rfcs/ directory structure with active/ and accepted/ subdirectories - Added docs/rfcs/README.md explaining the fresh start and directory structure - Added docs/rfcs/template.md RFC submission template - Updated docs/rfc.md to reference main repo instead of external datahub-project/rfcs - Updated docs-website/sidebars.js to include RFCs in navigation The external datahub-project/rfcs repository should be archived with a deprecation notice directing contributors to the main repository. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Update all RFC documentation to reference #contribute-code instead of #rfc, consolidating contribution discussions into a single channel. Changes: - Updated docs/rfc.md (3 references) - Updated docs/rfcs/README.md (1 reference) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
🔴 Meticulous spotted visual differences in 2 of 1067 screens tested: view and approve differences detected. Meticulous evaluated ~8 hours of user flows against your PR. Last updated for commit 6978224. This comment will update as new commits are pushed. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Fix several documentation build issues: - Comment out missing GraphQL reference docs (queries, mutations, objects, etc.) - Comment out missing Python SDK reference docs (builder, clients, sdk-v2, models, urns) - Exclude RFC template.md from doc generation to avoid JSX parsing errors - Remove markdown links to template.md to avoid broken link errors - Escape angle brackets in template.md title These changes fix sidebar validation errors and broken link errors while maintaining documentation structure. The commented-out sections can be re-enabled when the referenced documentation is generated. Note: Pre-existing broken links to graphql and python-sdk docs remain (not introduced by RFC migration changes). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
Migrate the RFC (Request for Comments) process from the separate datahub-project/rfcs repository back to the main DataHub repository to improve visibility and reduce contributor friction.
This represents a "fresh start" for RFCs - historical RFCs remain accessible in git history and the archived external repository, but will be migrated on an as-needed basis when they become relevant.
Changes
docs/rfcs/directory structure withactive/andaccepted/subdirectoriesdocs/rfcs/README.mdexplaining the fresh start and directory structuredocs/rfcs/template.mdRFC submission templatedocs/rfc.mdto reference main repo instead of external datahub-project/rfcsdocs-website/sidebars.jsto include RFCs in navigationNext Steps
After this PR is merged:
datahub-project/rfcsrepositoryTest Plan
generateDocsDir.ts)🤖 Generated with Claude Code