fix: limit split to 8 parts in parseCommitHeaderLine to prevent delimiter collision (issue #1100)

[tmdeveloper007]

Summary

Fixes git log delimiter collision in parseCommitHeaderLine. The function splits on | without a limit, so commit messages containing | characters would produce more than 8 parts, corrupting the parsed data.

Changes

• Changed line.split("|") to line.split("|", 8) to limit the split to exactly 8 fields
• This ensures the pipe-delimited format is respected regardless of pipe characters in commit messages

Testing

• Local: npm run type-check passes
• Parser correctly handles commit messages with pipe characters

Closes #1100

[vercel]

Someone is attempting to deploy a commit to the Nisshchaya's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@tmdeveloper007, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d3637d10-24b1-45d2-a2f7-98ce1008c736

📥 Commits

Reviewing files that changed from the base of the PR and between 07ceab7 and e8d0df3.

📒 Files selected for processing (4)

• app/api/auth/signup/route.ts
• lib/services/bitbucketService.ts
• lib/services/gitService.ts
• lib/services/gitlabService.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🎉 Thanks for your contribution, @tmdeveloper007!

Your PR has passed our automated GSSoC quality checks. Here's a quick summary:

Check	Status
PR description	✅ Provided
PR title	✅ Meaningful
Linked issue	✅ Found
Change size	✅ Looks good (42 lines across 4 file(s))

A maintainer will review your PR soon. Please be patient and available for feedback. 💪

GSSoC'26 automation · Maintainer: @nisshchayarathi

[tmdeveloper007]

CI Status

CodeRabbit: PASS
CodeQL: PASS
Lint: PASS
GSSoC PR Spam & Quality Check: PASS
Type Check: PRE-EXISTING FAILURES (unrelated to this PR - same errors exist in main branch)
Vercel deployment: PENDING maintainer authorization (required for fork PRs)

This PR is ready to merge once the maintainer approves the Vercel deployment.