di-sukharev / di-sukharev/opencommit
[Feature]: Exclude certain file types from the git diff command
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
I develop in python and of course the use of jupyter notebooks destroys nicely formatted git diffs. Currently, I use this tool by committing all my .py files with opencommit, then committing all my .ipynb files manually as a separate commit. Other file types, like images, should be excluded for similar reasons.
Suggested Solution
I would pass the contents of the git diff over all files except those from an excluded list. Optionally, you could include in the prompt the filenames of those that were changed but not included in the diff.
Alternatives
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named in the issue. Trace how the git diff command gathers changed files and passes them to the commit-message prompt. Done means excluded file types are omitted from the diff, with any included behavior for reporting omitted filenames defined and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100