Skip to content

docs: Enhance Customization Guide with Troubleshooting and FAQ Section - #9041

Closed
VanshikaSingh28 wants to merge 2 commits into
JhaSourav07:mainfrom
VanshikaSingh28:docs/troubleshooting-faq-customization-guide-6241
Closed

docs: Enhance Customization Guide with Troubleshooting and FAQ Section#9041
VanshikaSingh28 wants to merge 2 commits into
JhaSourav07:mainfrom
VanshikaSingh28:docs/troubleshooting-faq-customization-guide-6241

Conversation

@VanshikaSingh28

@VanshikaSingh28 VanshikaSingh28 commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes #6241

Pillar

  • 🎨 Pillar 1 — New Theme Design
  • 📐 Pillar 2 — Geometric SVG Improvement
  • 🕐 Pillar 3 — Timezone Logic Optimization
  • 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

Checklist before requesting a review:

  • I have read the CONTRIBUTING.md file.
  • I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
  • I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
  • My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
  • I have updated README.md if I added a new theme or URL parameter.
  • I have started the repo.
  • I have made sure that i have only one commit to merge in this PR.
  • The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
  • (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

@vercel

vercel Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

@VanshikaSingh28 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

@retenta-bot

retenta-bot Bot commented Aug 16, 2026

Copy link
Copy Markdown

This PR enhances the documentation by adding a Troubleshooting and FAQ section, which is crucial for user support and experience. It aligns with our previous decision to improve user experience through better documentation. If you have any questions or need further assistance, feel free to reach out. Happy coding!

@retenta-bot retenta-bot Bot changed the title docs: add Troubleshooting and FAQ section to customization guide (#6241) docs: Enhance Customization Guide with Troubleshooting and FAQ Section Aug 16, 2026
@github-actions

github-actions Bot commented Aug 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category PR Size Base Size Difference
Total JS 5005.04 KB 5005.04 KB 0 B
Total CSS 354.80 KB 354.80 KB 0 B

@Aamod007 Aamod007 added mentor:Aamod007 type:docs Documentation changes, wikis, or README updates level:beginner Small changes Usually isolated fixes or simple UI/text updates. labels Aug 16, 2026
Aamod007
Aamod007 requested changes Aug 16, 2026
View reviewed changes

@Aamod007 Aamod007 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

It looks like this PR adds the Table of Contents including the 'Troubleshooting & FAQ' link, but the actual 'Troubleshooting & FAQ' section content itself is missing from the diff! Could you please push the rest of the changes so the link actually points to something? Once the section is added, I'll be happy to approve.

@github-actions

github-actions Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

⚠️ Hey @VanshikaSingh28, this pull request has been inactive for 3 days. It will be automatically closed in 2 days if no further activity occurs.

If you are still working on this, please push your latest changes or leave a comment to keep it active.

@github-actions

github-actions Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

🤖 Hey @VanshikaSingh28, this pull request has been automatically closed because it has been inactive for 5 days.

Why was this PR closed?
To keep the repository manageable, we automatically close pull requests that have had no activity for 5 days.

How to reopen this PR:

  1. Pull the latest changes from the upstream repository
  2. Resolve any merge conflicts
  3. Address any review feedback
  4. Push your changes to your branch
  5. Reopen this PR by commenting /reopen or creating a new PR

We appreciate your contribution and would love to review your work when it's ready! Thank you! ❤️

@github-actions github-actions Bot added the inactive This PR was closed due to inactivity. label Aug 25, 2026
@github-actions github-actions Bot closed this Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Aamod007 Aamod007 Aamod007 requested changes

Assignees

No one assigned

Labels

inactive This PR was closed due to inactivity. level:beginner Small changes Usually isolated fixes or simple UI/text updates. mentor:Aamod007 type:docs Documentation changes, wikis, or README updates

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

docs: Add Troubleshooting and FAQ section to customization guide

2 participants

@VanshikaSingh28 @Aamod007