FabriceSalvaire/CodeReview

Reverse engineer gitk

Open

#32 opened on Nov 22, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (402 stars) (97 forks)batch import
PRIVATEgood first issuehelp wanted

Description

Tcl/Tk source: https://github.com/FabriceSalvaire/CodeReview/blob/master/ressources/gitk

  • list nice features
    • search in : commit message, filename, patch
  • how is painted graph ?
    • tag etc.

Contributor guide

Tech stack
None
Domain
desktopdeveloper experiencetooling
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
basic Git knowledgeTcl/Tk familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Examine the linked gitk source (Tcl/Tk) to reverse engineer its features like commit message search, filename search, patch search, and graph painting. Document how the graph is painted and list nice features. This issue requires understanding the gitk source code and possibly the CodeReview repository's Python/Qt5 code to inform similar features. No coding changes are expected, just research and documentation.
Reverse engineer gitk · FabriceSalvaire/CodeReview#32 | Good First Issue