2 Star 0 Fork 0

Git工具集 / GitSavvy

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
GitSavvy.sublime-settings 11.97 KB
一键复制 编辑 原始数据 按行查看 历史
{
/*
Change this to `false` if you don't wish to be prompted when
discarding files.
*/
"prompt_before_destructive_action": true,
/*
Uncomment the setting below to explicitly set which git binary
to use. An empty string will search PATH for "git". The setting may
be a direct string to a git binary, e.g.:
"git_path": "/usr/bin/git",
Or it may be a dictionary keyed off what sublime.platform() returns,
so it may be customized on a per-platform basis. e.g.:
"git_path": {
"default": "",
"windows": "C:/Program Files/Git/cmd/git.exe"
},
*/
"git_path": "",
/*
Set custom environment variables for git command execution.
*/
"env": {
},
/*
Change this to `true` when doing dev work on GitSavvy.
*/
"dev_mode": false,
/*
A list of tags (subsystems) to filter the output of debug.trace().
Only takes its effect when "dev_mode" is set to `true`.
*/
"dev_trace": [
"debug",
"reload"
],
/*
Enter your github API key in the field below. To interact with
a GitHub Enterprise instance, add a field with the FQDN as the key
and the API key as the value.
*/
"api_tokens": {
// "github.com": "ADD YOUR GITHUB TOKEN HERE"
// "gitlab.com": "ADD YOUR GITLAB TOKEN HERE"
},
/*
maximum number of items per page when requesting from github
*/
"github_per_page_max" : 100,
/*
maximum number of items per page when requesting from gitlab
*/
"gitlab_per_page_max" : 100,
/*
Change this to "full" to display a full diff for the current commit
when writing a commit message.
Change this to "stat" to display a diff stat for the current commit
when writing a commit message.
Change this to `false` to disable.
*/
"show_commit_diff": "stat",
/*
Change this to `false` to not scroll to the first hunk automatically when
you open the inline-diff view from the status dashboard.
*/
"inline_diff_auto_scroll": true,
"colors": {
"log_graph": {
"commit_dot_foreground": "#9911",
"commit_dot_background": "#991",
"path_foreground": "#991",
"path_background": "#99991109",
"matching_commit_foreground": "#1991",
"matching_commit_background": "#199"
}
},
/*
Change this to `true` when you would like inline diff to
ignore EOL whitespace changes.
See details in https://github.com/timbrel/GitSavvy/issues/177
*/
"inline_diff_ignore_eol_whitespaces": false,
/*
Add entries to this array (e.g. "pull" or "push") if you'd like the
output of these Git commands to always be shown in a panel.
*/
"show_panel_for": [],
/*
Add entries to this array (e.g. "pull" or "push") if you'd like any
open panel to be closed at the beginning of the operation.
*/
"close_panel_for": [],
/*
Whether git and githook output is logged live
If false, results are shown after execution.
*/
"live_panel_output": false,
/*
Command will exit if on the timeout if the timeout reached.
You may want to increase this if you have a slow disk or a very
large repository. If you think there is something GitSavvy can do
to prevent this long running git command, open an issue.
*/
"live_panel_output_timeout": 10000,
/*
https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#Commit-Guidelines
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 80 characters
It will use 'invalid.deprecated.line-too-long.git-commit' scope by default.
The warning is will be outlined instead of fully marked
*/
"pedantic_commit": true,
"pedantic_commit_ruler": true,
"pedantic_commit_first_line_length": 50,
"pedantic_commit_message_line_length": 72,
"pedantic_commit_warning_length": 20,
/*
Change this to `false` to suppress the input in the panel output.
*/
"show_input_in_output": true,
/*
Change this to `true` to print the stdin in the panel output.
*/
"show_stdin_in_output": false,
/*
Change this to `false` to suppress the elapsed time in the panel output.
*/
"show_time_elapsed_in_output": true,
/*
Change this to `false` to suppress Git status in ST3 status bar.
*/
"git_status_in_status_bar": true,
/*
When entering a tag message, this will be used if the message is empty.
The replacement value "{tag_name}" is optional, but recommended.
*/
"default_tag_message": "Tag {tag_name}",
/*
The filename for extra customized info to be displayed after the default
COMMIT_HELP_TEXT, such as commit message rules/tips/conventions.
Place this file at the root of the repo, and it should be commited to the
repo as well.
The file name defaults to `.commit_help`.
If this file is not presented, the functionality is totally ignored.
*/
"commit_help_extra_file": ".commit_help",
/*
For each command specified, always include the command line flags
indicated in the global_flags option AFTER the command.
*/
"global_flags": {
// --no-columns is not supported in Git versions <1.7.11. If Git is configured
// to use columns globally, --no-columns should be added here.
// "branch": ["--no-columns"]
//
// or, configure a GPG key to sign commits with a given key
// "commit": ["-S", "--gpg-sign=<key-id>"]
},
/*
For each command specified, always include the command line flags
indicated in the global_flags option BEFORE the command.
*/
"global_pre_flags": {
// for example, override settings via the "-c" option, e.g
// the following configures a gpg.program no-tty wrapper script
// "commit": ["-c", "gpg.program=./scripts/stgpg.sh"]
// and configure every commit to be signed with your key
// "commit": ["-c", "commit.gpgsign=true"]
},
/*
Prints branches sorted by recent commit (works with git 2.7.0+)
https://www.kernel.org/pub/software/scm/git/docs/git-branch.html
Change this to `true` to sort branches by recent.
Change this to `false` to sort branches by alphanumeric.
*/
"sort_by_recent_in_branch_dashboard": false,
/*
Set this to `true` to display remotes in the branch dashboard by default.
*/
"show_remotes_in_branch_dashboard": false,
/*
Set this to `true` to display remotes in the tags dashboard by default.
*/
"show_remotes_in_tags_dashboard": false,
/*
Limit the number of tags listed in the tags dashboard.
*/
"max_items_in_tags_dashboard": -1,
/*
When set to `true`, GitSavvy will offer to set the upstream on `git: push`
when tracking branch is not configured.
*/
"prompt_for_tracking_branch": true,
/*
When set to `true`, GitSavvy will automatically display more info about the
current commit in a output panel.
*/
"log_show_more_commit_info": true,
/*
Diffstat look like
core/commands/blame.py | 13 +++++--------
core/commands/log.py | 9 +++------
core/git_mixins/history.py | 8 ++------
3 files changed, 10 insertions(+), 20 deletions(-)
Set to `false` if don't want to show this when view a commit or diff.
*/
"show_diffstat": true,
/*
When set to `true`, GitSavvy will automatically display more info about the
current commit in a output panel. When set to `false`, this function must
be invoked manually.
*/
"graph_show_more_commit_info": true,
/*
When set to `true,`, GitSavvy will display the full diff of the current
commit in the output panel.
*/
"show_full_commit_info": false,
/*
When set to `true`, GitSavvy will follow file renames when running git log/graph
*/
"log_follow_rename": false,
/*
When set to `true`, GitSavvy will follow file renames in blame view
*/
"blame_follow_rename": false,
/*
Set it to "file", "commit" or "all_commits" to specify the default detection
method for the blame view.
*/
"blame_detect_move_or_copy_within": "file",
/*
When set to `true`, GitSavvy will prompt for confirmation when closing
the commit message view. Ignored when "commit_on_close" is true.
*/
"prompt_on_abort_commit": true,
/*
When set to `true`, GitSavvy will display git-flow integration commands.
*/
"show_git_flow_commands": false,
/*
When set to `true`, GitSavvy will include the `--log` flag when performing
merges. This will mean commit summaries will be included in the merge commit
message.
*/
"merge_log": true,
/*
The default base for the rebase dashboard.
*/
"rebase_default_base_ref": "",
/*
When set to `true`, rebase dashboard uses preserve-merges mode when opened.
*/
"rebase_preserve_merges": false,
/*
When set to `true`, GitSavvy will prompt for confirmation before actually
performing a `git push --force` operation.
*/
"confirm_force_push": true,
/*
When set to `true`, closing the commit message window via keyboard will result
in a commit action being taken, except in cases where the message is empty.
The same is also true for amending commits.
*/
"commit_on_close": false,
/*
This encoding will be used whenever Git's output cannot be correctly parsed
as UTF-8. Modify this value if you regularly with files and Git history
with a different text encoding.
Example:
"fallback_encoding": "gbk"
*/
"fallback_encoding": "windows-1252",
/*
This setting should only be set to true in the following conditions:
- you have installed the "Codecs33" package from Package Control
- you are running Linux or OS X
- you would like to use non-supported codecs like "gbk" for the
`fallback_encoding` value
*/
"load_additional_codecs": false,
/*
GitSavvy allows you to press `Tab` to cycle from one dashboard interface
to the next. This setting defines the order of that cycle. The following
are valid entries, and can be included in your preferred order:
status
branch
rebase
tags
graph
*/
"tab_order": [
"status",
"branch",
"rebase",
"tags",
"graph"
],
/*
Set this value to a valid git reset mode (e.g. --hard, --soft) to skip
reset mode prompt and always use that reset mode.
*/
"use_reset_mode": null,
/*
When set to `true`, you can navigate the dashboards by using arrow keys.
*/
"arrow_keys_navigation": false,
/*
When set to `true`, GitSavvy will become Vintagoues friendly.
You might need to restart Sublime in order to get this working.
*/
"vintageous_friendly": false,
/*
When set to `true`, all views will start in INSERT mode.
Ignored if `vintageous_friendly` is `false`.
*/
"vintageous_enter_insert_mode": false,
/*
When set to `true`, all views will hide their help menu when rendering.
You can still toggle the help menu by pressing `?`.
*/
"hide_help_menu": false,
/*
When set to `true`, no views will receive the prompt asking to initialize
Git in the current view's directory when not found.
*/
"disable_git_init_prompt": false
}
Python
1
https://gitee.com/vcs-all-in-one/GitSavvy.git
git@gitee.com:vcs-all-in-one/GitSavvy.git
vcs-all-in-one
GitSavvy
GitSavvy
master

搜索帮助