Skip to content

Plan to transfer repository into tree-sitter organization #81

@takegue

Description

@takegue

from https://github.com/tree-sitter-grammars/.github/blob/main/CONTRIBUTING.md#requirements-for-inclusion

If you'd like your grammar to be included in this organization, please adhere to the following:

  1. Include corpus tests to ensure the parser works as expected.
    • You may also include some example files to be parsed in CI.
  2. The queries must use the last-wins precedence (all queries are applied).
    • Include highlight queries and their tests. Other queries are generally not necessary.
    • The highlight captures should either use [Tree-sitter][STANDARD_CAPTURE_NAMES]'s
      "standard" names, or [Neovim][treesitter-highlight-groups]'s names.
  3. The external scanner (if any) must be written in C and not C++.
  4. The grammar must be written in JavaScript and not TypeScript or anything else.
  5. You should be somewhat active in maintaining it. It's fine if there's no need for
    maintenance, but you shouldn't let issues pile up for months to years on end.
  6. You must follow [SemVer] for your grammar: breaking changes must result in a major bump,
    new features in a minor bump, and bug fixes in a patch bump.
  7. Commit messages should follow the [Conventional Commits] specification.
  8. Make sure all the metadata (names, links, versions, etc.) are correct and consistent.
    • For example, the version in package.json must be the same as the one in `C

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions