[CHORE] Break out attribution.mdx content into separate file#385
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a stable marker in the attribution documentation so an external release automation (release DAG) can deterministically locate where to inject generated attribution content when opening release PRs.
Changes:
- Inserted an HTML comment marker (
GENERATED_ATTRIBUTION_START) immediately after the attribution screenshot to serve as an insertion point for automated content generation.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
b214385 to
9b753ec
Compare
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
attribution.mdx content into seperate file
Break out the generated attribution content from attribution.mdx into _generated_attribution.mdx, imported as a component. The release DAG can overwrite the data file without touching the parent page's formatting. Signed-off-by: Adam Lastowka <[email protected]> Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Adam Lastowka <[email protected]>
ae548a9 to
2f5fa66
Compare
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
|
staging deploy broken but the page looks fine locally |
attribution.mdx content into seperate fileattribution.mdx content into separate file
Closes #386
Pull Request
Adds a comment so that the release DAG knows where to insert the attribution artifact contents when it opens a PR (see here)