Far-Beyond-Pulsar/Pulsar-Native

Improvements to the Git identity panel

Closed

#486 opened on Jul 30, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (29 forks)auto 404
Cross-platformdifficulty: mediumenhancementgood first issuehelp wantedux/design

Repository metrics

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

Description

Expanding the git identity panel created in #470 with new features such as:

  • Git Hooks
  • Git Auto-refresh interval (Continuously fetch to notify users of important changes) (And possibly more, this is left up to the implementor!)

Important:

repo-specific configurations such as hooks can be configured globally. The engine will need to store these in the already existing app data folders used for logging, settings, etc. On startup during the splash screen we need to add a step that checks project git hooks against those configured in the engine's global hooks config and add anything that is missing. This is a project-specific FS op and must go through Engine_FS meaning Engine_FS may need to be extended to support safe wrappers for FS manipulation of a project's .gir directory

Contributor guide

Research direction
The issue asks to extend the existing Git identity panel with Git Hooks and auto refresh. Start by reviewing the implementation of the Git identity panel from PR #470 to understand current UI and engine interactions. Then, explore the Engine FS module to see how project specific filesystem operations are currently handled, as the issue mentions extending it with safe wrappers for the project's .gir directory. Study the startup sequence during the splash screen to find where to add a check for hooks configurations. Finally, look into the global configuration storage (app data directories) to understand how to store global hooks. This research will help you design the necessary changes.
Tech stack
rust
Domain
desktopdeveloper 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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45