Skip to content

Latest commit

 

History

History
64 lines (45 loc) · 1.82 KB

CONTRIUTING.md

File metadata and controls

64 lines (45 loc) · 1.82 KB

Contributing

We have a few guidelines to follow when contributing to this Repo:

Commit Convention

Before you create a Pull Request, please make sure your commit message follows the Conventional Commits specification.

Commit Message Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Type

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

Example:

feat: add new feature
description : this feature very good

Pull Request

  • The main branch is the source of truth and should always reflect the latest stable release.
  • Create a new branch for each feature or bug fix.
  • Make sure to add tests for your changes.
  • When creating a pull request, please provide a clear and concise description of the changes made.
  • If you include a video or screenshot, would be awesome so we can see the changes in action.
  • If your pull request fixes an open issue, please reference the issue in the pull request description.
  • Once your pull request is merged, you will be automatically added as a contributor to the project.

steps

  1. Fork GitToGet Repo
  2. clone your fork git clone url
  3. make a branch git branch name
  4. do your changes it this branch
  5. push your changes in your fork
  6. make a pull request