-
Notifications
You must be signed in to change notification settings - Fork 62
Add "Back to Top" Links in README for Better Navigation #140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Back to Top" Links in README for Better Navigation #140
Conversation
✅ Deploy Preview for github-spy ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughA Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 Thank you @Aripilli-Bhavana for your contribution. Please make sure your PR follows https://github.com/GitMetricsLab/github_tracker/blob/main/CONTRIBUTING.md#-pull-request-guidelines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
README.md (1)
149-158: Inline styles will be stripped & extra blank lines add noise
- GitHub’s sanitizer removes the
styleattribute, so the button styling will not survive.- Five empty lines + a second horizontal rule produce unnecessary vertical whitespace.
A cleaner, markdown-native alternative:
- ---- - -<p align="center"> - <a href="#top" style="font-size: 18px; padding: 8px 16px; display: inline-block; border: 1px solid #ccc; border-radius: 6px; text-decoration: none;"> - ⬆️ Back to Top - </a> -</p> +<p align="center">[⬆️ Back to Top](#top)</p>This keeps the link centered without relying on stripped HTML/CSS and removes superfluous blank lines.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(2 hunks)
🔇 Additional comments (1)
README.md (1)
2-2:<!-- top -->is not a functional anchor on GitHub-rendered MarkdownA plain HTML comment does not create an element with
id="top", sohref="#top"relies on browsers falling back to “scroll to beginning” (which is inconsistent) rather than a guaranteed anchor. Either drop the custom target and link to GitHub’s built-in#readme, or emit a real anchor element.-<!-- top --> +<a id="top"></a>Please open the README in the GitHub UI and confirm the link actually scrolls; if it doesn’t, adopt the fix above or switch the link to
#readme.
|
🎉🎉 Thank you for your contribution! Your PR #140 has been merged! 🎉🎉 |
The current README.md is too long and contains multiple sections. Scrolling through it can be cumbersome, especially for new users or contributors accessing it on smaller screens.
💡 Proposed Solution
Add [🔝 Back to Top] links at the end of major sections in the README
Optionally add a top anchor like (though GitHub supports #readme by default)
Maintain consistent formatting across all sections
Issue number #139
Summary by CodeRabbit