timbrel / gitsavvy Goto Github PK

If you have a branch in the git flow style you name them things like feature/registration. Unfortunately right now your status view will show a name like that as just feature

Most of the outputs in this plugin is done to the status bar.
I would like to see an option to output to panels, especially for certain actions like commit or push where you'd want to see the output, like a response from the server(s).

Add a distinct style guide for the commit messages:

• First line should be max 50 characters
• Second line should be empty
• Any subsequent lines should be max 72 characters

Coloring the background of any characters that exceed limits is ideal, only warning the user.

This should be optional, of course.

References:
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
https://github.com/blog/926-shiny-new-commit-styles

• show all local tags
• add tag
• delete tag
• show tags on remote (?)
• push tags to remote

Add basic documentation including:

• intro / welcome
• command palette commands
• special views, their features, and key-bindings
• existing GitHub integration features
  • setup API keys
• docs include context for what it going on under the hood, to help learn git (moved from #12)

Link to docs from README.

Currently just removes everything including and after the COMMIT_HELP_TEXT. Instead, add a canonical separator below which all content will be excluded. Follow-up to #45.

• help docs written in markdown in docs/
• wiki-style browsing when user presses super-enter on link
• open docs to specific page/location when certain flags are set on originating view
• docs include context for what it going on under the hood, to help learn git moving this requirement to #28.

I get the attached error message, the color scheme defaults to white with black text, and the changed hunks are unclear (in cached mode it seems like the changed hunks aren't shown at all, in uncached mode the hunks are shown as white text on black but it isn't clear what was removed, changed, added).

The default background colors result in a very low contrast because I'm using a light color scheme.
Is there a way to set these color values in the user config?
If not, would you consider to add in the config?

themeGenerator.add_scoped_style("GitSavvy Added Line", "git_savvy.change.addition", background="#37A832")
themeGenerator.add_scoped_style("GitSavvy Removed Line", "git_savvy.change.removal", background="#A83732")

Thanks.

• When path to git cannot be found, notify user and inform that they can either install or enter custom path in User/GitSavvy.sublime-settings.
• When Git name and email and unconfigured, notify user, prompt for name/email, and configure Git.

There's no easy way of telling which hunks or lines are actually staged in the inline diff.
Consider adding a background color to these (e.g. yellow) to distinguish them.

This would be especially useful with #35.

Cache last diff to be applied; when undo is invoked, apply the same diff with --reverse toggled.

Add setting to allow signed and/or signed-off commits instead of "regular" commit.

• list all issues for remote repository (special view)
• syntax highlighting
• open new issue (special view)
• close issue
• view details for issue, including comment history
• add comment
• view issue in browser

https://developer.github.com/v3/issues/

For debugging purposes (particularly for those submitting bugs), store the stdin and stdout of the most recent failed git operation. Add command to open web browser with URL along the these lines:

https://github.com/divmain/GitSavvy/issues/new?title=failed%20git%20command%20X&body=some%0Ainput%0Aand%0Aoutput

Leaving this here as a feature request. How hard/easy it is to support Bitbucket as well?

There should be mention in the README that this is for Sublime Text 3 only and wont work on older versions.

Special view with:

• list of all submodules with commit status
• summary for each submodule
• initialize new submodule
• update

This would be a nice to have feature. See this repo for details on its implementation https://github.com/nvie/gitflow

Also, deleted files should appear different in the status view somehow.

• list all open pull requests (special view)
• show details for pull request, including comment history (special view)
• show changes (?) (special view)
• open pull request in browser
• open new pull request against remote branch
• open new pull request against remote owner/repo/branch

https://developer.github.com/v3/pulls/

This isn't a real ticket.

When in the inline-diff view, you cannot do SUPER-L, as this results in a locked machine. Introduce Windows-specific keybindings that swap SUPER for CTRL across the board.

• Before running git commands, display what is about to happen to the user
• Dry-run mode where commands aren't run, just displayed to the user

• syntax highlighted view
• pressing super+enter on a branch name checks out that branch
• pressing super+enter on a commit will checkout that commit as detached HEAD
• pressing enter on a commit displays the full commit message and diff in a separate window

Instead of:

• root
  • commands
    • git-related commands
    • github-related commands
  • common
    • util
      • actual common code
    • git-related code
    • github-related code
    • some actual common code (view or HTTP related)
  • syntax
    • ...

Consider:

• root
  • core
    • all git-related commands and shared code
  • github
    • all github-related commands and shared code
  • common
    • http
    • view-related
    • theme-related
    • date-related
    • file-related
    • log / debug
    • etc
  • syntax

Follow-up for changes seen in #45.

• convert commit view to ui.Interface
• enable region-based retrieval of commit message
• toggle-able display of relevant diff
• toggle-able display of commit summary (ala git commit --dry-run, see #107)
• add embedded syntax-highlighting for diff (defining scope for region)
• investigate: stage files from commit view

When creating a commit, it's handy to see at a glance what you are actually committing, a diff displayed at the bottom is the optimal solution.

Should also be optional, as it would probably add extra load time on larger commits.

• syntax-highlighted view
• show all local branches
• checkout branch
• delete branch (--force)
• merge branch

For instance, displaying the status of a branch named bug/1234 will output a branch name of bug.

Using git update-index --assume-unchanged, git update-index --no-assume-unchanged and git ls-files -v where files are marked as "assume unchanged" if first char in output is h.

Moved from #28.

Basically the option to customize this line: https://github.com/divmain/GitSavvy/blob/83a486eaad8aac982160caabeb7099052da5e462/core/commands/log_graph.py#L29

git 1.9.3
sublime 3065
ubuntu linux 14.04

Traceback (most recent call last):
  File "/opt/sublime_text/sublime_plugin.py", line 543, in run_
    return self.run(edit, **args)
  File "/home/oliver/.config/sublime-text-3/Packages/GitSavvy/core/commands/blame.py", line 39, in run
    content = self.get_content()
  File "/home/oliver/.config/sublime-text-3/Packages/GitSavvy/core/commands/blame.py", line 50, in get_content
    blamed_lines, commits = self.parse_blame(blame_porcelain.splitlines())
  File "/home/oliver/.config/sublime-text-3/Packages/GitSavvy/core/commands/blame.py", line 100, in parse_blame
    k, v = re.match(r"([^ ]+) (.+)", next_line).groups()
AttributeError: 'NoneType' object has no attribute 'groups'

Relates to #7.

Can we have a new feature that show repo status in bottom left-hand corner of Sublime Text Window?

Include option for user to specify other merge tool.

Required merge functionality:

• git: merge
• git: abort merge
• git: merge (rebase) (split out as #26)
• git: fetch and merge
• status view reports merge status successfully
  • header
  • files
• merge information in commit view
• git: restart merge (untenable at present)
• git: restart merge for file...
• disallow inline-diff for file with merge conflict (patch is no longer two-way; it involves working tree, HEAD, and other branch/ref)

• icons for inserted, modified lines
• icon between lines for removed lines
• gray out icons when changes are staged

Thoughts for a rebase dashboard.

  REBASE:  master --> my-feature-branch
  STATUS:  conflict at 221ca4

    ┳ (dcc578)
    ┃
    ✔  11dc57  some commit message
    ┃
    ✔  d0c116  some other commit message
    ┃          resolved: path/to/some/file.ext
    ┃
  ▸ ✕  221ca4  message for commit with conflict
    ┃          conflict: path/to/some/conflicting/file.ext
    ┃          resolved: path/to/file/already/resolved.ext
    ┃
    ?  a0891c  message for commit to check next
    ┃
    ?  5fe330  message for last commit
    ┃
    ┻

  ###############                      #############
  ## CONFLICTS ##                      ## COMMITS ##
  ###############                      #############

  [o] open file                        [s] squash commit with next
  [a] accept file in current state     [S] squash all commits
  [m] use mine                         [u] move commit up (above previous)
  [t] use theirs                       [d] move commit down (below next)
  [M] launch external merge tool       [e] edit commit message

  ####################
  ## REBASE ACTIONS ##
  ####################

  [R] restart rebase
  [A] abort rebase
  [F] finalize rebase

-

Notes:

• cannot finalize until all commits show a green check mark
• squash commands would take to commit-like view pre-filled with combined commit messages
• cannot squash all until all commits show a green check mark
• cannot squash commit with next until selected and selected's next commit show green check mark