[OSSCA 2024] Applying & Githru VSCode Extension Review

링크 정보를 불러오는 중...

This open‑source project is a VSCode extension that visually analyzes Git metadata.

I had previously used Git GUI tools such as SourceTree or Git Graph. However, I often ran into errors and eventually ended up using Git Bash again. Even so, the visual advantages of GUI tools were always something I missed.

Githru attempts to fill that gap by providing visual insights into commit structures and contribution patterns while still working alongside Git Bash or the built‑in VSCode Git features.

Because the application process included a small pre‑task, I actually installed and ran the extension beforehand. The README suggested running npm build:all in the Getting Started section, but no matter how many times I tried, the command did not work.

Instead, I installed the extension directly in VSCode, ran it in debug mode, entered a Git token, and was able to access it through the bottom panel just like other extensions.

The pre‑task asked applicants to describe something that felt lacking or could be improved, so I tried to analyze the tool from several angles while using it.

Things That Felt Incomplete

UX

On the right side of the interface, the extension visually displays the file structure and contributor percentages.

The animation when navigating the file structure is smooth and the UI is generally clean. However, the "go back" interaction felt slightly unclear.

For example, when navigating deeper into the file tree and returning to the parent directory, it would be easier to understand the navigation flow if the parent node appeared on the left side as a visible reference.

Similarly, when switching from viewing commits of a specific contributor back to the overall contributor view, a clearer back interaction would make the navigation feel more natural.

Another small issue was the large graph shown at the top of the interface. It represents code counts over time, but at first glance it felt somewhat abstract. Displaying exact values on hover would likely make the information easier to understand.

UI

Allowing users to choose a custom point color using RGB values is an interesting idea.

However, the way the color is applied feels slightly ambiguous. When selecting a color, it is applied immediately to the current branch being viewed, while other branches still retain their previous colors. Only after restarting or reconnecting to Githru does the selected color appear across all branches.

From an interaction perspective, this behavior feels inconsistent. If a user changes the color, it would be clearer if the system either:

• applied the color to all branches immediately, or
• treated it as a branch‑specific setting that consistently applies only to that branch.

Clarifying this rule would likely improve the UX.

Another thing I noticed was that most interface colors look very similar in tone. Because graphs, folder structures, and other visual elements share almost the same color intensity, the visual hierarchy is not very strong.

If the interface introduced a color system with several brightness or tone variations (for example four or five related shades), the readability of graphs and structural information could improve significantly.

However, since the system allows users to freely pick RGB values, automatically generating such color variations might be difficult. Two possible alternatives came to mind:

• providing a few preset color themes, or
• defining a default project color palette and deriving related shades from it.

This approach could preserve user customization while keeping the interface visually consistent and easier to read.

Documentation

Finally, I also felt that the documentation could be improved.

When entering the GitHub repository for the first time, the README emphasized contributor information quite prominently, while explanations about the project itself were relatively limited.

Other open‑source projects, such as ArgoCD, provided more detailed documentation about installation steps and project structure, which made it much easier for newcomers to understand the project quickly.

Improving the documentation could make this project more approachable for first‑time users and contributors.

Overall, the project felt clean and focused, including only the necessary features without unnecessary complexity.

I also became curious about how the visualization would behave when analyzing much larger repositories.

After exploring the tool this way, I felt that there were several areas where I could potentially contribute, which ultimately led me to apply to this project.

• #Retrospect
• #Open Source
• #Review