[Git Files] Add Git Files package

Git/Comments.tmPreferences

@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<plist version="1.0">
+<dict>
+	<key>name</key>
+	<string>Comments</string>
+	<key>scope</key>
+	<string>source.gitcommit, source.gitconfig, source.gitrebase</string>
+	<key>settings</key>
+	<dict>
+		<key>shellVariables</key>
+		<array>
+			<dict>
+				<key>name</key>
+				<string>TM_COMMENT_START</string>
+				<key>value</key>
+				<string># </string>
+			</dict>
+		</array>
+	</dict>
+</dict>
+</plist>

Git/Snippets/section.sublime-snippet

@@ -0,0 +1,9 @@
+<snippet>
+	<content><![CDATA[
+[${1:section}]
+	$0
+]]></content>
+	<tabTrigger>section</tabTrigger>
+	<scope>source.gitconfig</scope>
+	<description>[section]</description>
+</snippet>

Git/Symbol List.tmPreferences

@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<plist version="1.0">
+<dict>
+	<key>name</key>
+	<string>Symbol List</string>
+	<key>scope</key>
+	<string>meta.brackets.gitconfig</string>
+	<key>settings</key>
+	<dict>
+		<key>showInSymbolList</key>
+		<integer>1</integer>
+	</dict>
+</dict>
+</plist>

Git/commit.sublime-syntax

@@ -0,0 +1,81 @@
+%YAML 1.2
+---
+# Highlight regular git commits, merge commits, and tags.
+
+name: Git Commit
+file_extensions:
+  - COMMIT_EDITMSG
+  - MERGE_MSG
+  - TAG_EDITMSG
+scope: text.gitcommit
+
+contexts:
+  prototype:
+    - include: comments
+
+  main:
+    - include: commit-message
+
+  branch-line:
+    - match: \bOn branch\s+(.*)
+      captures:
+        1: support.type.branch-name.gitcommit
+
+  change:
+    - match: (new file|modified|deleted)\s*(:)\s*(.*)
+      captures:
+        1: keyword.change-list.change.gitcommit
+        2: punctuation.separator.change.gitcommit
+        3: keyword.change-list.file.gitcommit
+
+  change-list:
+    - include: change-list-header
+    - include: change
+
+  change-list-header:
+    - match: '\bChanges to be committed\s*(:)'
+      scope: keyword.change-list.heading.gitcommit
+      captures:
+        1: punctuation.separator.change-list.gitcommit
+
+  comments:
+    - match: '#'
+      scope: punctuation.definition.comment.gitcommit
+      push:
+        - meta_scope: comment.line.gitcommit
+        - match: \n
+          pop: true
+        - include: change-list
+        - include: branch-line
+        - include: date-line
+
+  commit-message:
+    # this absurd regex is necessary to:
+    #   1. match comments in the subject line
+    #   2. only style the first 50 chars in the subject line
+    - match: ([^#\n]{,50})[^#\n]*((#).*$)?
+      captures:
+        1: string.unquoted.subject-line.gitcommit markup.heading.gitcommit
+        2: comment.line.gitcommit
+        3: punctuation.definition.comment.gitcommit
+      push:
+        # enforce empty line following subject line
+        - match: \n
+          push:
+            - match: \n
+              pop: true
+            - match: '.+$'
+              scope: invalid.missing-newline.gitcommit
+        # everything left that isn't a comment is the commit message
+        - match: '[^#]*'
+          scope: text.plain.commit-message.gitcommit
+          push:
+            - match: '[^#]*'
+              scope: text.plain.commit-message.gitcommit
+
+  # apply a meta scope to the commit date
+  date-line:
+    - match: \bDate\s*(:)\s*(.*)
+      captures:
+        1: punctuation.separator.date.gitcommit
+        2: meta.commit-date.gitcommit

Git/config.sublime-syntax

@@ -0,0 +1,206 @@
+%YAML 1.2
+---
+# Syntax based on documentation here:
+# https://git-scm.com/docs/git-config#_syntax
+
+name: Git Config
+file_extensions:
+  - gitconfig                # /etc/gitconfig
+  - .gitconfig               # ~/.gitconfig
+first_line_match: ^\[core\]  # .git/config files always start with [core]
+scope: source.gitconfig
+
+variables:
+  escape_char: \\"bnt
+  section_name: '[\w.-]+(?=[\s\]])'  # lookahead catches missing space, e.g. color"branch".
+  space_or_eol: (?=(?:\s|$))         # makes values on last line match properly
+  variable_name: '[a-zA-Z][\w-]*'
+  zero_to_255: 25[0-5]|2[0-4][0-9]|1\d\d|[1-9][0-9]|[0-9]
+
+contexts:
+  prototype:
+    - include: comments
+
+  main:
+    - include: section
+
+  boolean:
+    # 0 and 1 are omitted due to mismatches (e.g. "log -1", "HEAD~1"). They will
+    # be matched as unquoted strings instead.
+    - match: \b(?:yes|true|on|off|no|false){{space_or_eol}}
+      scope: constant.language.gitconfig
+
+  color:
+    - include: color-named      # red, blue, green
+    - include: color-attribute  # bold, italic, underline
+    - include: color-numeric    # 0-255
+
+  color-attribute:
+    - match: \b(?:no-?)?(?:ul|strike|reverse|italic|dim|bold|blink){{space_or_eol}}
+      scope: support.constant.color-attribute.gitconfig
+
+  color-named:
+    - match: \b(?:yellow|white|red|normal|magenta|green|cyan|blue|black|auto){{space_or_eol}}
+      scope: support.constant.color.gitconfig
+
+  color-numeric:
+    - match: '\b(?:{{zero_to_255}}){{space_or_eol}}'
+      scope: constant.other.color.rgb-value.gitconfig
+
+  comments:
+    - match: '[#;]'
+      scope: punctuation.definition.comment.gitconfig
+      push:
+        - meta_scope: comment.line.gitconfig
+        - match: $\n?  # consume newline so completions aren't shown at EOL when
+          pop: true    # typing comments
+
+  # The only valid escapes: '\b', '\n', '\t', '\"', '\\'.
+  escape:
+    - include: trailing-slash
+    - match: \\[^{{escape_char}}]
+      scope: invalid.illegal.escape.gitconfig
+    - match: \\[{{escape_char}}]
+      scope: constant.character.escape.gitconfig
+
+  illegal-newline:
+    - match: \n
+      scope: invalid.illegal.gitconfig
+
+  illegal-slash:
+    - match: \\
+      scope: invalid.illegal.gitconfig
+
+  # changed = red
+  # untracked = bold green
+  key-color-pair:
+    - match: ^\s*({{variable_name}})\s*(\=)
+      captures:
+        1: variable.other.readwrite.gitconfig
+        2: keyword.operator.assignment.gitconfig
+      push:
+        - meta_scope: meta.key-value-pair.gitconfig
+        - meta_content_scope: meta.value.gitconfig
+        - match: '(?=^\s*{{variable_name}}\s*\=)'  # next key-value pair
+          pop: true
+        - match: (?=^\s*\[)                        # start of new section
+          pop: true
+        - include: color
+
+  # key = val
+  key-value-pair:
+    - match: ^\s*({{variable_name}})\s*(\=)
+      captures:
+        1: variable.other.readwrite.gitconfig
+        2: keyword.operator.assignment.gitconfig
+      push:
+        - meta_scope: meta.key-value-pair.gitconfig
+        - meta_content_scope: meta.value.gitconfig
+        - match: '(?=^\s*{{variable_name}}\s*\=)'  # next key-value pair
+          pop: true
+        - match: (?=^\s*\[)                        # start of new section
+          pop: true
+        - include: value
+
+  # [section "subsection"]
+  section-header:
+    - match: \[
+      scope: punctuation.definition.section.begin.gitconfig
+      push:
+        - meta_scope: meta.brackets.gitconfig
+        - match: \]
+          scope: punctuation.definition.section.end.gitconfig
+          pop: true
+        - include: illegal-newline  # complain if '[' and ']' on separate lines
+        - include: illegal-slash
+        - include: subsection-name
+        - include: section-name
+    - include: stray-bracket
+
+  # A section is a [section header] and the list of key-value pairs under it.
+  #
+  # [section "subsection"]
+  #   key1 = value1
+  #   key2 = value2
+  section:
+    # [color] subsections are matched separately, because they are the only
+    # sections that take colors for values.
+    - include: section-color  # e.g. [color "branch"], [color "status"]
+    - include: section-other
+
+  # We only want to match color values under these subsections:
+  #   [color "branch"]
+  #   [color "diff"]
+  #   [color "interactive"]
+  #   [color "status"]
+  # Note that this does not match [color] (without the subsection). This is
+  # because [color] doesn't actually take color values.
+  section-color:
+    - match: ^\s*(?=\[\s*color\s+\")
+      push:
+        - match: (?=^\s*\[) # start of new section
+          pop: true
+        - include: section-header
+        - include: key-color-pair
+
+  section-name:
+    - match: '{{section_name}}'
+      scope: entity.name.gitconfig
+
+  # section-other matches all sections except [color "subsection"].
+  section-other:
+    - match: ^\s*(?=\[)
+      push:
+        - match: (?=^\s*\[) # start of new section
+          pop: true
+        - include: section-header
+        - include: key-value-pair
+
+  stray-bracket:
+    - match: \]
+      scope: punctuation.definition.section.end.gitconfig invalid.illegal.stray-bracket.gitconfig
+
+  string:
+    - match: '"'
+      scope: punctuation.definition.string.begin.gitconfig
+      push:
+        - meta_include_prototype: false
+        - meta_scope: string.quoted.double.gitconfig
+        - match: '"'
+          scope: punctuation.definition.string.end.gitconfig
+          pop: true
+        - include: escape
+        - include: illegal-newline  # newlines only permitting after trailing \
+
+  # [section "subsection"]
+  # Subsections are not normal strings. Escapes (e.g. \", \t) and trailing
+  # slashes are not recognized. Newlines are illegal.
+  subsection-name:
+    - match: '"'
+      scope: punctuation.definition.string.begin.gitconfig
+      push:
+        - meta_include_prototype: false
+        - meta_scope: string.quoted.double.gitconfig
+        # '\' is legal in a subsection name, but in front of the trailing '"'
+        # it prevents the '"' from terminating the string. \" is not an escape.
+        # It is still interpreted as two characters.
+        - match: \\"  # no scope needed
+        - match: '"'
+          scope: punctuation.definition.string.end.gitconfig
+          pop: true
+        - include: illegal-newline
+
+  # Trailing slashes can be used to break up long lines. '\' is only legal at
+  # the end of a line, or in an escape such as '\"'. Anywhere else it will cause
+  # a fatal parser error. Comments are not permitted after a trailing slash.
+  trailing-slash:
+    - match: (\\)\s*$
+      captures:
+        1: constant.character.escape.gitconfig
+
+  value:
+    - include: escape   # \", \\, \t
+    - include: string
+    - include: boolean  # true, yes, on, off, no, false
+    - match: \S         # match most values
+      scope: string.unquoted.value.gitconfig

Git/rebase.sublime-syntax

@@ -0,0 +1,58 @@
+%YAML 1.2
+---
+# Highlight interactive rebase text (git rebase -i).
+
+name: Git Rebase
+file_extensions:
+  - git-rebase-todo
+first_line_match: '^(?:pick|squash|reword|fixup|exec|edit|drop) \h{7,} '
+scope: source.gitrebase
+
+variables:
+  hash: \h{7,}
+
+contexts:
+  prototype:
+    - include: comments
+
+  main:
+    - include: commit
+
+  comments:
+    - match: '#'
+      scope: punctuation.definition.comment.gitrebase
+      push:
+        - meta_scope: comment.line.gitrebase
+        - match: \n
+          pop: true
+        - include: rebase-msg
+
+  # e.g. pick d284bb2 Initial commit
+  commit:
+    - match: ^\s*(squash|reword|pick|fixup|exec|edit|drop|x|s|r|p|f|e|d)[\t ]
+      captures:
+        1: storage.type.edit.gitrebase
+      push:
+        - meta_scope: meta.commit.gitrebase
+        - match: \n
+          pop: true
+        - match: \b({{hash}})\s # e.g. d284bb2
+          captures:
+            1: constant.numeric.hex.hash.gitrebase
+          push:
+            - meta_content_scope: text.plain.commit-msg.gitrebase
+            - match: $
+              pop: true
+
+  # e.g. Rebase 9e73d21..6746220 onto 9e73d21 (2 commands)
+  # highlight the hashes in this comment
+  rebase-msg:
+    - match: '\bRebase\s+'
+      push:
+        - meta_scope: meta.rebase-msg.gitrebase
+        - match: '$'
+          pop: true
+        - match: '\b{{hash}}\b'
+          scope: constant.numeric.hex.hash.gitrebase
+        - match: \.\.
+          scope: keyword.operator.commit-range.gitrebase