We have a few guidelines to follow when contributing to this Repo:
Before you create a Pull Request, please make sure your commit message follows the Conventional Commits specification.
<type>[optional scope]: <description>
[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
Example:
feat: add new feature
description : this feature very good
- 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.
- Fork GitToGet Repo
- clone your fork
git clone url
- make a branch
git branch name
- do your changes it this branch
- push your changes in your fork
- make a pull request