Describe the solution you'd like
In the log view, labes should indicate:

• Current HEAD
• Head of all branches (local and remote)
• Tags

Diff view shows only unstaged diffs as of now. It should also show staged diffs.

Put these actions on a toolbar:

• Pull
• Push
• Commit
• Continue rebase
• Abort rebase

Describe the bug
In commit popup, only the subject of the commit is editable.

Expected behavior
Whe should be able to edit both subject and body parts.

git diff HEAD@{2} HEAD@{1} > patch
git checkout HEAD@{2}
git apply patch

Check if repo is a gerrit repo:

• In .git/hooks/commit-msg, check presence of "Gerrit" and "add_ChangeId()"
• In file .git/config, section [remote "origin"], variable url, check for presence of "gerrit"
• Example:
  • [remote "origin"]
    • url = ssh:// < username > @ gerrit.xxx.xxx:29418/some_repo

If repo is marked as gerrit repo:

• Push to "origin HEAD:refs/for/" instead of "origin branch"
  • Hint: branch=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
  • Hint: git push origin HEAD:refs/for/$branch
• Ability to copy the remote commit-msg to .git/hooks/
  • Hint: scp -p -P 29418 < your username > @ < your Gerrit review server > :hooks/commit-msg < local path to your git > /.git/hooks/

Create a CRepository class that holds all the models instead of CTreeFileModel holding them.
Since there are two file models, one class should rule them all.

Add to commit context menu:

• Branch from this

Git command:
git checkout -b < branchname > < sha1-of-commit >

Git command for ASCII graph:
git log --graph --all --pretty=format:"%h | %s | %an | %aI"
(Commit Id, subject, author, date)

Git command for commit hash and parents hash:
git log --pretty="%H %P"

For embedded diff:
https://github.com/google/diff-match-patch

Show n lines of context in diff:
--unified=< n >

Check if local is ahead of remote:
git rev-list origin..HEAD

Check if local is behing remote:
git rev-list HEAD..origin

Graph drawing:
strathausen/dracula

• Make controller aware of repository type (Git or SVN)
• Create feature flags in CCommands (can rebase, can push, etc...)
• Create CSVNCommands, inherits CCommands

Parse diff lines and use colors to show additions and deletions.

Describe the bug
"Expand all" and "Collapse all" buttons in tree view don't do anything.

To Reproduce
Steps to reproduce the behavior:

1. Open a repo with some subfolders
2. Select "View -> Files as a tree"
3. Click on 'Expand all'

Expected behavior
All tree nodes should expand.

• Add clickable header columns, with sort direction indicator
• Transmit sort selection to controller
• Implement sorting in models

Describe the solution you'd like

• From a log menu, select the commit to rebase on
• In a list view, view the commit's child commits and change their order
• Apply or cancel

Describe alternatives you've considered

• In a console:
  • git rebase -i .....
  • change order of lines in text file

• Allow multiple diff and blame views.
• Add panes by subdiving existing ones
• Choose content of every pane:
  • Files
  • Log
  • Graph
  • Diff
  • Blame
  • Output

Add a simple command to abort rebase.

The app should take a guess at the "smartest" action to do. A button could be dedicated to that action.
Examples:

• Current branch is more than n commits behind : "Pull" (Save stash, pull, pop stash)
• Current branch is more than n commits ahead : "Push"
• Working tree has some staged files: "Commit"
  ...

Many components don't have a focus indicator, which makes it hard to guess where focus is...

CGitCommands:

• Make commands that modify files stackable

CRepository:

• Improve file status update: not just a model reset but row by row update

• Real time output of cloning process
• Select cloned repository tab on finished

Describe the solution you'd like
The command line executed when issuing commands should be visible and editable before being executed. A nice place would be the status bar.

Describe alternatives you've considered
The only alternative is to execute the command in the console.

Describe the solution you'd like

• Mark a commit as "left commit"
• Mark a commit as "right commit"
• View the result in the diff view

Describe alternatives you've considered
Git on console.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.