Skip to content

fix: update GitHub stars count in header component#706

Open
dipanshurdev wants to merge 1 commit intoOpenCut-app:mainfrom
dipanshurdev:minor-patch
Open

fix: update GitHub stars count in header component#706
dipanshurdev wants to merge 1 commit intoOpenCut-app:mainfrom
dipanshurdev:minor-patch

Conversation

@dipanshurdev
Copy link
Contributor

@dipanshurdev dipanshurdev commented Feb 17, 2026

📊 Update GitHub Stars Count

Description

Updates the GitHub stars badge in the header component to reflect the current repository stars (now at 45.9k+).

Changes

  • Updated GitHub stars display: 40k+45.9k+ in header.tsx

Type of Change

  • Minor update

Testing

  • Verified in local development

Summary by CodeRabbit

Release Notes

  • Chores
    • Updated the displayed GitHub follower count in the header to reflect the latest statistics.

@netlify
Copy link

netlify bot commented Feb 17, 2026

👷 Deploy request for appcut pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit bf5c096

@vercel
Copy link

vercel bot commented Feb 17, 2026

@dipanshurdev is attempting to deploy a commit to the OpenCut OSS Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 17, 2026

📝 Walkthrough

Walkthrough

Updates the displayed GitHub follower count in the header component from "40k+" to "45.9k+". This is a straightforward value update to reflect current follower metrics in the social buttons section.

Changes

Cohort / File(s) Summary
Header Follower Count
apps/web/src/components/header.tsx
Updated hardcoded GitHub follower display from "40k+" to "45.9k+".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • add: github stars count #28: Modifies the same GitHub count display in header.tsx but implements dynamic star fetching and rendering instead of a hardcoded value.

Poem

🐰 The counter hops up with glee,
From forty to forty-five-point-nine you see,
A follower milestone, oh what delight!
The header now shines with updated might! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description significantly deviates from the required template, which explicitly states the project is not accepting non-critical bug fixes without prior issue and maintainer approval. Follow the repository's PR template: open an issue first, obtain maintainer approval for bug fixes, or explain why this is a critical exception to the stated policy.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title correctly identifies the main change: updating the GitHub stars count in the header component from 40k+ to 45.9k+.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
apps/web/src/components/header.tsx (1)

71-74: Consider fetching the GitHub star count dynamically instead of hardcoding it.

This value has already gone stale once (40k+ → 45.9k+) and will again. You could fetch it at build time or via the GitHub API (e.g., using an ISR route or a server component) so it stays current without manual patches.

If you prefer to keep it static for simplicity, at minimum add a comment noting this is a manually-maintained value so future contributors know to update it.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/web/src/components/header.tsx` around lines 71 - 74, The GitHub star
count is hardcoded in the Header component render (the Button containing
HugeiconsIcon/GithubIcon) and should be made dynamic or at least documented;
replace the literal "45.9k+" with a prop/state value fetched from the GitHub API
(e.g., call the REST API for repo.stargazers_count in a server component,
getStaticProps/getStaticPaths or an ISR route and pass it into the Header, or
fetch on mount and set state) and ensure caching/TTL to avoid rate limits, or if
you opt to keep it static, add a clear inline comment above the Button
explaining that the value is manually maintained and must be updated when stars
change. Ensure you update references in header.tsx where the
Button/GithubIcon/HugeiconsIcon are rendered so the UI uses the fetched prop
(e.g., starsCount) instead of the hardcoded string.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@apps/web/src/components/header.tsx`:
- Around line 71-74: The GitHub star count is hardcoded in the Header component
render (the Button containing HugeiconsIcon/GithubIcon) and should be made
dynamic or at least documented; replace the literal "45.9k+" with a prop/state
value fetched from the GitHub API (e.g., call the REST API for
repo.stargazers_count in a server component, getStaticProps/getStaticPaths or an
ISR route and pass it into the Header, or fetch on mount and set state) and
ensure caching/TTL to avoid rate limits, or if you opt to keep it static, add a
clear inline comment above the Button explaining that the value is manually
maintained and must be updated when stars change. Ensure you update references
in header.tsx where the Button/GithubIcon/HugeiconsIcon are rendered so the UI
uses the fetched prop (e.g., starsCount) instead of the hardcoded string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments