git-deps shows unrelated commits when dependency of 'merge' commits are checked
- Dominant language
- Python
- Stars
- 319
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the git-deps tool for linux kernel backporting work.
When git-deps is run to find any dependent commits in linux kernel there is a chance it encounters 'merge' commits. git-deps output is very huge when it checks dependency for 'merge' commits and git-deps needs to be stopped manually since it runs for a very long time.
Maybe '--no-merges' needs to be used to avoid merge commits?
Contributor guide
Research direction
Start by reproducing the report with git-deps on a history containing merge commits, using the Linux kernel backporting scenario described. Trace the dependency output for a merge commit and compare it with the expected relevant commits; it is done when unrelated commits are excluded and the command completes without needing manual interruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100