gitconfig file
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Store a .gitconfig file for keeping track of modifications:
Also [add an alias](https://git-scm.com/book/ms/v2/Git-Basics-Git-Aliases) to clean up
`git branch -vv | grep ': gone] ' | awk '{print $1}' | xargs git branch -D`
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 reviewing the repository's existing dotfiles and determine where the requested .gitconfig should live. Add the configuration and the documented alias for cleaning up gone branches, then verify that the file contains the requested alias and can be used as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100