tree-sitter-gitcommit
tree-sitter-gitcommit copied to clipboard
gbprod
A tree-sitter grammar for gitcommit messages
Hello and thanks for the parser! Just wanted to raise the issue that overflow is not detected for body segments that contain something like `BREAKING CHANGE` or a generic trailer...
https://github.com/gbprod/tree-sitter-gitcommit/issues/46#issuecomment-1993961811
See https://github.com/nvim-treesitter/nvim-treesitter/issues/5774#issuecomment-1852679457 And https://github.com/gbprod/tree-sitter-gitcommit/pull/48#discussion_r1424519492
Currently, syntax highlighting assumes `#` is the comment character used in Git Commit messages. The comment character used in Git Commit messages can be configured using `core.commentChar` in `.gitconfig`. That...
For Github / Gitlab / Gitea and others they all support common keywords for referencing issues in a commit message: https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword Such as `Closes #1` It would be nice to...
Compilation is really slow ```bash tree-sitter build --wasm --output gitcommit.wasm --reuse-allocator ```
`typechange`: file type changed (regular file, symbolic link or submodule) ### Example ```ini # typechange: after/ftplugin/svelte.vim ``` ### Parse tree #### Current ```clojure (generated_comment ; [13, 0] - [13, 39]...
When `config.commentChar` is different than `#` diff highlighting is not working. I changed `config.commentChar` to be `%` instead of the default `#` since this conflicts with Markdown when I'm using...
