Link to Computational Physics Group website#1168
Conversation
Add group website link to README contact section and docs landing page footer for better discoverability. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
📝 WalkthroughWalkthroughAdded attribution and contact information to the README.md Getting Started section, including affiliation with Computational Physics Group at Georgia Tech and contact details for Spencer Bryngelson. Also added a corresponding hyperlink to the Computational Physics Group website in the documentation footer. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sequence DiagramThis PR adds a static link to the Computational Physics Group website in the README contact section and the docs landing page footer. The diagram shows the high-level flow from the developer's change through CI and deployment to the rendered README and docs site. sequenceDiagram
participant Developer
participant Repository
participant CI
participant GitHubPages
participant User
Developer->>Repository: Create PR modifying README.md and docs/index.html (add group link)
Repository->>CI: Trigger CI build for PR
CI-->>Repository: Build & tests pass
Repository->>GitHubPages: Merge & deploy documentation
GitHubPages-->>User: Docs landing shows footer with Computational Physics Group link
Repository-->>User: GitHub README renders with Computational Physics Group link
Generated by CodeAnt AI |
There was a problem hiding this comment.
Pull request overview
This PR adds static links to the Computational Physics Group website to improve visibility and attribution. The links are placed in high-visibility locations (README contact section and docs landing page footer) with zero maintenance overhead.
Changes:
- Add group website link to README contact section with contextual text about MFC development
- Add styled link to docs footer with amber accent color next to the existing copyright
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| README.md | Adds a new line crediting the Computational Physics Group at Georgia Tech as MFC developers with a hyperlink |
| docs/index.html | Adds a second link in the footer to the Computational Physics Group website with amber styling |
Nitpicks 🔍
|
|
CodeAnt AI finished reviewing your PR. |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
docs/index.html (1)
250-252: Duplicate link destination in footer — consider consolidating.Lines 250 and 251 both link to
https://comp-physics.group/: the existing copyright anchor text ("Spencer H. Bryngelson and Tim Colonius") and the new explicit group label. Adjacent links to the same URL are redundant and can confuse screen readers, which will announce two separate link targets pointing to the same page.Additionally, the existing copyright
<a>at line 250 has no styling class (renders as undecorated white text), while the new link at line 251 usestext-amber-400 hover:underline, creating a visual inconsistency within the same line.Consider removing the hyperlink from the copyright names and keeping only the new descriptive link:
♻️ Proposed consolidation
- © <span id="copyright-year"></span> <a href="https://comp-physics.group/">Spencer H. Bryngelson and Tim Colonius</a> - · <a href="https://comp-physics.group/" class="text-amber-400 hover:underline">Computational Physics Group @ Georgia Tech</a> + © <span id="copyright-year"></span> Spencer H. Bryngelson and Tim Colonius + · <a href="https://comp-physics.group/" class="text-amber-400 hover:underline">Computational Physics Group @ Georgia Tech</a>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/index.html` around lines 250 - 252, Consolidate the duplicate footer links by removing the hyperlink from the "Spencer H. Bryngelson and Tim Colonius" anchor and leaving the styled "Computational Physics Group @ Georgia Tech" link as the single link target; locate the elements around the span with id="copyright-year" and replace or adjust the first <a> (text "Spencer H. Bryngelson and Tim Colonius") so it is plain text (no href/class) while keeping the second <a> with class="text-amber-400 hover:underline" as the accessible, styled link to https://comp-physics.group/.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/index.html`:
- Around line 250-252: Consolidate the duplicate footer links by removing the
hyperlink from the "Spencer H. Bryngelson and Tim Colonius" anchor and leaving
the styled "Computational Physics Group @ Georgia Tech" link as the single link
target; locate the elements around the span with id="copyright-year" and replace
or adjust the first <a> (text "Spencer H. Bryngelson and Tim Colonius") so it is
plain text (no href/class) while keeping the second <a> with
class="text-amber-400 hover:underline" as the accessible, styled link to
https://comp-physics.group/.
User description
Summary
These are static links — zero maintenance.
Test plan
🤖 Generated with Claude Code
CodeAnt-AI Description
Add Computational Physics Group link to README and docs footer
What Changed
Impact
✅ Easier to find the Computational Physics Group website✅ Clearer project affiliation and attribution✅ Faster access to group contact and collaborator information💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit