Context
The file is named Readme.md (capital R, lowercase rest). GitHub
redirects both casings to one canonical URL, but other tools don't
— for example, the Streamlit Cloud image is case-sensitive and
will 404 a link that says readme.md. The GitHub norm and the
norm most Linux tooling expects is README.md.
What to change
git mv Readme.md README.md (this preserves file history).- Run
grep -rIn 'Readme.md' . and update every internal link
(especially in the tree blocks and the "What Is This" pointer).
- Confirm the file still renders on GitHub: the repo's homepage
should show the README content as before, with no broken-image
or 404 banner.
How to verify
ls README.md succeeds; ls Readme.md fails.grep -rIn 'Readme.md' . returns nothing (case-sensitive).git log --follow README.md shows the full history of the
renamed file.
Skill: trivial, but tests you on git mv semantics.
Estimated effort: S.
Context
The file is named
Readme.md(capital R, lowercase rest). GitHubredirects both casings to one canonical URL, but other tools don't
— for example, the Streamlit Cloud image is case-sensitive and
will 404 a link that says
readme.md. The GitHub norm and thenorm most Linux tooling expects is
README.md.What to change
git mv Readme.md README.md(this preserves file history).grep -rIn 'Readme.md' .and update every internal link(especially in the tree blocks and the "What Is This" pointer).
should show the README content as before, with no broken-image
or 404 banner.
How to verify
ls README.mdsucceeds;ls Readme.mdfails.grep -rIn 'Readme.md' .returns nothing (case-sensitive).git log --follow README.mdshows the full history of therenamed file.
Skill: trivial, but tests you on
git mvsemantics.Estimated effort: S.