Madhusolanki48 / Madhusolanki48/LeetCode-Practice
Help with prevention of extra commits
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Everytime on submitting some question on leetcode, there are multiple files that gets created while the same code is begin pushed on github.
Tool: LeetHub V2 [[link](https://chromewebstore.google.com/detail/leethub-v2/mhanfgfagplhgemhjfeolkkdidbakocm?hl=en)]
Redundant file names:
- Updated stats
- Update README - Topic Tags
- Create README - LeetHub
These are getting committed every single time.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce a LeetCode submission with LeetHub V2 and inspect the resulting commits for “Updated stats,” “Update README - Topic Tags,” and “Create README - LeetHub.” Determine whether the redundant commits can be prevented or whether the issue belongs in LeetHub V2; done means submissions no longer create those unnecessary commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100