Skip to content

Conversation

@cdzombak
Copy link
Owner

@cdzombak cdzombak commented Nov 3, 2025

When a file ends with "commitentry", the marker is now stripped from the content before creating Day One entries or Things tasks. The marker is still used internally to determine if a file should be committed, but it won't appear in the final output sent to integrations.

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an issue where trailing "commitentry" markers were not being removed from file content during processing. Files now have these markers automatically cleaned up when detected as the last non-empty line.

When a file ends with "commitentry", the marker is now stripped from
the content before creating Day One entries or Things tasks. The marker
is still used internally to determine if a file should be committed,
but it won't appear in the final output sent to integrations.
@coderabbitai
Copy link

coderabbitai bot commented Nov 3, 2025

Walkthrough

The processFile function in files.go now detects and removes the trailing "commitentry" line from file content when it is the last non-empty line, updating the Content field accordingly.

Changes

Cohort / File(s) Summary
Trailing line removal
files.go
After determining the last non-empty line, removes the trailing "commitentry" line from content if detected and updates the Content field

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • Verify the condition that checks for "commitentry" is correct and handles edge cases
  • Confirm the line removal logic properly updates the Content field
  • Check if this removal should apply to all file types or only specific ones

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The pull request title "Remove commitentry suffix from entries" directly and accurately describes the main change in the changeset. The modification in files.go removes the trailing "commitentry" marker from file content when detected, which is precisely what the title conveys. The title is concise, specific, and avoids vague terminology or noise, making it clear to someone reviewing the git history what the primary change accomplishes.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude/remove-commitentry-suffix-011CUjybjjbQMwTVqVtEEa8H

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b1da860 and 98ca5f0.

📒 Files selected for processing (1)
  • files.go (1 hunks)
🧰 Additional context used
🪛 GitHub Actions: PR #3
files.go

[error] 136-136: sys.Birthtimespec undefined (type *"syscall".Stat_t has no field or method Birthtimespec)


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

@cdzombak cdzombak merged commit a8b6376 into main Nov 3, 2025
12 checks passed
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.

3 participants