# Contributing to the Graphcast CLI Welcome to Graphcast CLI! Thanks a ton for your interest in contributing. If you run into any problems feel free to create an issue. PRs are much appreciated for simple things. If it's something more complex we'd appreciate having a quick chat in GitHub Issues or the Graph Discord server. Join the conversation on [the Graph Discord](https://thegraph.com/discord). Please follow the [Code of Conduct](https://github.com/graphops/graphcast-sdk/blob/main/CODE_OF_CONDUCT.md) for all the communications and at events. Thank you! ## Commit messages and pull requests We follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). In brief, each commit message consists of a header, with optional body and footer: ``` [optional scope]: [optional body] [optional footer(s)] ``` `` must be one of the following: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests - chore: Changes to the build process or auxiliary tools and libraries such as documentation generation - revert: If the commit reverts a previous commit, contains the header of the reverted commit. Make sure to include an exclamation mark after the commit type and scope if there is a breaking change. `` optional and could be anything that specifies the place of the commit change, e.g. solver, [filename], tests, lib, ... we are not very restrictive on the scope. The scope should just be lowercase and if possible contain of a single word. `` contains succinct description of the change with imperative, present tense. don't capitalize first letter, and no dot (.) at the end. `` include the motivation for the change, use the imperative, present tense `