aspiers/git-deps

idea: blame-deps (aka 3D-blame)

Open

#43 opened on Mar 2, 2015

View on GitHub
 (9 comments) (2 reactions) (0 assignees)Python (55 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (318 stars)
PR merge metrics
 (PR metrics pending)

Description

The idea is to do something like

git deps some-file.txt

This will open the git-deps browser with the contents of the file loaded into a pane in a typical blame view:

e5392d87  1) This is some file.
e5392d87  2) =====================================
e5392d87  3)
69d951f2  4) Look at all the nice contents.
e5392d87  5)

The magical thing is that each of the revisions are clickable - doing so will open the git-deps graph for the clicked commit.

Contributor guide

Research direction
Explore how git blame output can be parsed and linked to git deps commit dependency graph. Look at existing git deps code for handling commits and UI.
Tech stack
python
Domain
clideveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50