Repository navigation
docs: fix python README LICENSE link and stale release wording - #26
Merged
yonib05 merged 1 commit intoJul 17, 2026
Merged
Conversation
The python README linked [LICENSE](LICENSE) but the file lives at the repo root, one level up — broken in the template view. Point it at ../LICENSE like the TypeScript README, and teach the hoist rewrite to flip it back to LICENSE when the package moves to the root. Also update the root README's release-tag note: the setup script now drops the dual-prefix scheme automatically during hoist, so the manual suggestion was stale.
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
1 participant
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.
Description
Two small docs fixes:
python/README.mdLICENSE link was broken. It linked[LICENSE](LICENSE)but the file lives at the repo root. Now links../LICENSE(matching the TypeScript README), and the setup script's hoist rewrite flips it back toLICENSEwhen the package moves to the root — verified end-to-end: template view resolves, hoisted view resolves.Root README release wording was stale. It suggested users manually "drop the dual-prefix scheme" after setup, but since fix(setup): repair TS setup script and exercise both scripts in CI #22 the setup script rewrites the tag scheme automatically during hoist.
Testing
[LICENSE](LICENSE)with the file present at rootpy_compileon the setup scriptChecklist