feat(source-control): complete git panel workflow#259
Conversation
…ement for source control panel
…out in SourceControlPanel
…ommit feedback styling
…-handoff # Conflicts: # src/app/App.tsx
|
@crynta Hi, do you have an estimated timeline for implementing this control panel feature? Version control support is really important for day-to-day use in Terax, so I wanted to check whether this is likely to land soon or if it is still expected to take a bit more time. Thanks. |
|
@viniraioli Hi, thanks for asking, I’m actually looking at this right now and gonna merge it soon. It was originally supposed to be included in 0.6.6, but there were a couple of pretty obvious terminal issues I wanted to fix first, especially after the BetterStack video (btw, thanks to them for that :) ). So I decided to quickly fix those, ship the release, and then move on to new features like source control, the new AI agents workflow, improved web preview, extensions, etc. with source control being the first priority |
…-handoff # Conflicts: # src-tauri/src/modules/net.rs
What
Completes the Git source control workflow with a polished source-control panel, status count badge, staged/unstaged groups, discard actions, commit/push affordances, and AI-generated Conventional Commit messages for staged changes.
This continues the inactive draft work in #174 and turns the source-control surface into a usable review/stage/commit flow.
Why
Closes #194
Closes #243
Closes #87
Refs #1
Terax users need a first-class Git workflow for reviewing AI-generated changes without leaving the app or falling back to another editor. The existing draft PR #174 already established the direction; this PR picks up that work and fills in the missing workflow polish.
How
git_discardcommand and backend discard support for tracked and untracked files.Testing
pnpm exec tsc --noEmitcleansrc-tauri/)cargo checkcleanpnpm tauri devScreenshots / GIFs
Notes for reviewer
Related PR: #174 is the existing draft source-control implementation this follows up on.