aspiers / aspiers/git-deps

Excluding commits previously cherry-picked.

Open
#101 2 comments 0 reactions 0 assignees View on GitHub
enhancement question
Dominant language
Python
Stars
319
Forks
55
PR merge metrics
No merged PRs in 30d

Description

I'm trying to use git deps to optimize the backported work that I'm doing, and due to the massive size of the repo, if I don't exclude things that have already been backported it is impossible to glean any data. However, it appears that git deps "-e" only works if that exact commit is in the branch you're excluding, not if there is already a cherry-pick of that commit in the branch.

Does that make sense?

Please let me know if this functionality does exist and I'm just missing it.

Very cool piece of software and I'm hoping I'll be able to use it :)

Contributor guide

Open the contributing guide

Research direction

Start by reading the git deps "-e" behavior and how it matches commits in an excluded branch, then compare that with the issue's cherry-picked-commit case. Done means previously cherry-picked commits are excluded as intended, while existing exclusion behavior remains correct; the payload names no files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, python
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.