Fix README.md#1283
Conversation
|
|
|
Warning Review limit reached
Your plan currently allows 2 reviews/hour. Refill in 18 minutes and 36 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. WalkthroughThe PR updates README.md branding and asset references: banner, demo, and architecture diagram sources now point to ChangesREADME Branding and Asset Refresh
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (3 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 |
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 39-46: The README contains hardcoded hrefs mixing
"/releases/latest/download" with a versioned filename (seen on the Windows,
macOS, and Debian download anchor tags / images), which will 404 when the latest
release changes; update those three anchor hrefs either to fully pinned URLs
using the release tag and matching filenames (e.g.,
"/releases/download/v1.1.0/…") or change them to point users to the OS-specific
release page (e.g., the repository's "/releases/latest" or the general release
page) so filenames aren't required; ensure the Windows download anchor, the
macOS download anchor, and the Debian download anchor are all updated
consistently and verify the alt text/button images remain the same.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c94eaadb-fc65-42af-b051-6ad924ac628c
⛔ Files ignored due to path filters (8)
docs/assets/readme-assets/architectual-design-dark.svgis excluded by!**/*.svgdocs/assets/readme-assets/architectual-design-light.svgis excluded by!**/*.svgdocs/assets/readme-assets/banner.pngis excluded by!**/*.pngdocs/assets/readme-assets/btn-debian.svgis excluded by!**/*.svgdocs/assets/readme-assets/btn-github.svgis excluded by!**/*.svgdocs/assets/readme-assets/btn-macos.svgis excluded by!**/*.svgdocs/assets/readme-assets/btn-windows.svgis excluded by!**/*.svgdocs/assets/readme-assets/demo.pngis excluded by!**/*.png
📒 Files selected for processing (1)
README.md
| <a href="https://github.com/AOSSIE-Org/PictoPy/releases/latest/download/PictoPy_1.1.0_x64-setup.exe" style="display:inline-flex;align-items:center;"> | ||
| <img src="docs/assets/readme-assets/btn-windows.svg" alt="Windows download button" style="height:34px;width:auto;" /> | ||
| </a> | ||
| <a href="https://github.com/AOSSIE-Org/PictoPy/releases/latest/download/PictoPy_aarch64.app.tar.gz" style="display:inline-flex;align-items:center;"> | ||
| <img src="docs/assets/readme-assets/btn-macos.svg" alt="macOS download button" style="height:34px;width:auto;" /> | ||
| </a> | ||
| <a href="https://github.com/AOSSIE-Org/PictoPy/releases/latest/download/PictoPy_1.1.0_amd64.deb" style="display:inline-flex;align-items:center;"> | ||
| <img src="docs/assets/readme-assets/btn-debian.svg" alt="Debian download button" style="height:34px;width:auto;" /> |
There was a problem hiding this comment.
Use stable release-link strategy for OS download URLs.
These links mix releases/latest/download with versioned artifact names (PictoPy_1.1.0_...). When “latest” advances and filenames change, these URLs can 404.
Prefer either:
- pinning both tag and filename (e.g.
/releases/download/v1.1.0/...), or - linking users to the latest release page per OS instead of versioned direct assets.
As per coding guidelines, "Confirm that the code meets the project's requirements and objectives".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` around lines 39 - 46, The README contains hardcoded hrefs mixing
"/releases/latest/download" with a versioned filename (seen on the Windows,
macOS, and Debian download anchor tags / images), which will 404 when the latest
release changes; update those three anchor hrefs either to fully pinned URLs
using the release tag and matching filenames (e.g.,
"/releases/download/v1.1.0/…") or change them to point users to the OS-specific
release page (e.g., the repository's "/releases/latest" or the general release
page) so filenames aren't required; ensure the Windows download anchor, the
macOS download anchor, and the Debian download anchor are all updated
consistently and verify the alt text/button images remain the same.
|
|
1 similar comment
|
|
Updated download links for various platforms in the README.
|
|
1 participant
Summary by CodeRabbit