git summary
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
Hello,
I have a suggestion. Now "git summary" is working well but it has only a little use as it cannot filtered out file types in a project. For example, I work for a ruby on rails project, and it contains a lot of vendor files which are not created by our team, but it must exists in the repo as we might change a little bit on them such as color and fonts. Our major work are on *.rb files an *.erb files and *.js files and *.css files.
So if the summary accepts to filter file types. I think it will be helpful.
Thanks!
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
Start by locating the git summary command and reading how it currently selects files and parses arguments. Define a file-type filter for the requested extensions, then verify that the summary excludes non-matching files while preserving existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100