https://github.com/joshcamas/gitgud
A simple unity-based git client with a focus on extendability
https://github.com/joshcamas/gitgud
git unity3d
Last synced: 7 months ago
JSON representation
A simple unity-based git client with a focus on extendability
- Host: GitHub
- URL: https://github.com/joshcamas/gitgud
- Owner: joshcamas
- Created: 2018-12-11T18:05:33.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-02-04T15:37:47.000Z (almost 7 years ago)
- Last Synced: 2025-04-23T21:48:37.022Z (7 months ago)
- Topics: git, unity3d
- Language: C#
- Homepage:
- Size: 105 KB
- Stars: 8
- Watchers: 0
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# GitGud
A simple unity-based git client with a focus on extendability
### Features
* Simple settings
* Stage / Unstage
* Icons
* Attribute-based hooks
* Basic commit history
* Committing
* Stashing
* Discard all / Reset
* Push
* View stashes
* Checkout specific commit
### Features Coming Soon
* Redesign Error catching
* Better interface
### Wanted Features Someday
* Branching
* LFS locking
* Merge conflict resolvers
* Plugin API
* File tree visual
* File tree filters
* Async!!
## Attribute Hooks
There are currently 4 ways to hook into GitGud:
**PathContext:**
Adds a context option to specific fileviewers. (Currently staged and unstaged)
**CommitContext:**
Adds a context option to a specific commit list (Currently history only)
**Tab:**
Adds a tab to the GitGud window.
**TopButton:**
Adds a button to the top bar in the GitGud window.
***Documentation to come soon***
# Design Goals
The goal of this tool is to keep things light - a base interface, with all of the commands needed to make it work. However, just keeping things light would be boring! Thus, I'm designing the tool to be as extendable as possible, so new features can be added. I plan on creating several plugins myself, such as a meta file manager (hiding away those pesky meta files, an resolving conflicts related to them) - of course, these plugins will be kept separate from the main repo
Since this project just started, I haven't written any docs yet. When the api starts to find solid ground, I'll be sure to do that - documentation is very important ^_^