Contributing
Thank you for expressing your interest in contributing to CorgiSwap!
Corgi is an open-source project. If you want to contribute to the project, this section is here to guide you through your first steps with the Corgi team
Before starting any development, we highly encourage you to submit an issue on Github in order to discuss the problem, and the solution with the team. If you want to reach out to the dev team directly, contact @MichaellDang on Telegram.
- 1.Fork the repository and an add upstream remote. E.g.
- 2.Make sure you have the latest version of the default branch (
developormaster)$ git checkout develop$ git pull upstream develop - 3.Create your own branch and install dependencies$ git checkout -b branch-name$ yarn
- 4.Happy coding 🎉
We try to maintain as much consistency as we can between each of our repository. Your pull request has more chances to be accepted if you follow some the following rules, and write high quality code. Let's get started 💪
Check the UI Kit before you start doing anything. A lot of components are already created, and we don't want that you waste your time reinventing the wheel 😉
If a variant of a component needs to be created, use the corresponding component in the UI Kit as a base.
Most of our repos use Typescript, ESLint, and Prettier. Make sure you are familiar with Typescript’s best practices, and enable an ESLint and Prettier plugin for your IDE.
Make sure your code is formatted with Prettier, and is free from any ESLint error before you submit a pull request.
- Use Composition over Inheritance.
- Keep in mind that your code will be read and maintained by several other developers. Make it as clear and easy to update as possible.
Our commit messages follow Conventional Commits using commitlint.
Type | Description |
build | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
ci | Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) |
docs | Documentation only changes |
feat | A new feature |
fix | A bug fix |
perf | A code change that improves performance |
refactor | A code change that neither fixes a bug nor adds a feature |
style | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
test | Adding missing tests or correcting existing tests |
More at Angular's guidelines
Your code is ready to be submitted for review, congratulations🥳
- All pull requests must have a description of what the PR is trying to accomplish.
- Keep pull requests as small as possible. Larger pull requests should be broken up into smaller chunks with a dedicated base branch. Please tag the PR's that are merging into your base branch with the
epictag. - If possible self-review your PR and add comments where additional clarification is needed.
Create a draft PR as soon as possible so we can view your ongoing progress.
Thanks your for helping us making Corgi even more awesome ❤
Last modified 2yr ago