# Contributing to GraphQL Testx

Thank you for your interest in contributing to the GraphQL-TestX project
:heart_eyes::tada:

Before contributing please read an set of the guidelines for contributing to
**GraphQL Testx**: These are mostly guidelines, not rules. Use your best
judgment, and feel free to propose changes to this document in a pull request.

## Table of Contents

- [Code of Conduct](#code-of-conduct)
- [Pull Requests Guideline](#pull-requests-guideline)
- [Git Commit Messages Style Guide](#git-commit-messages-style-guide)

## Code of Conduct

This project applies the
[Mozilla Code of Conduct](https://www.mozilla.org/en-US/about/governance/policies/participation/).
By participating, you are expected to uphold this code.

## Pull Requests Guideline

Contributions to **GraphQL Testx** are made via
[Github Pull Requests](https://help.github.com/en/articles/about-pull-requests).

You can access this
[tutorial](https://gist.github.com/Chaser324/ce0505fbed06b947d962) to learn the
general flow of creating a fork and submitting your Pull Request.

The reviewer(s) may ask you to complete additional design work, tests, or other
changes before your pull request can be ultimately accepted.

## Git Commit Messages Style Guide

For git commit messages in general we use this
[style](https://seesparkbox.com/foundry/semantic_commit_messages).

If the description of your changes is long and can't be resumed in a short
comment line, consider reading this
[guideline](http://karma-runner.github.io/0.10/dev/git-commit-msg.html) for a
more complex and detailed commit message.

> **Tip:** Use `git commit` command to open an editor in the terminal and you
> will be able to edit the commit message any way you want :wink:
