Thanks for your interest in contributing to Fuel Wallet! This document outlines the process for installing dependencies and setting up Fuel Wallet for development, as well as some conventions to improve your contributions.
If you run into any difficulties getting started, you can always ask questions on our Discord .
There are many ways in which you may contribute to the Fuel Wallet project, some of which involve coding knowledge and some which do not. A few examples include:
Check out our Help Wanted or Good First Issues to find a suitable task.
If you are planning something big, for example, related to multiple components or changes current behaviors, make sure to open an issue to discuss with us before starting on the implementation.
This is a rough outline of what a contributor's workflow looks like:
changeset
to your PR.
pnpm changeset
- follow the prompt and add a description of your change at the end pnpm changeset:empty
- if no packages are being bumped breaking
label to your PR. 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 or correcting existing tests 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) chore:
- Other changes that don't modify src
or test files revert:
- Reverts a previous commit Thanks for your contributions!
Pull requests should be linked to at least one issue in the same repo.
If the pull request resolves the relevant issues, and you want GitHub to close these issues automatically after it merged into the default branch, you can use the syntax (KEYWORD #ISSUE-NUMBER
) like this:
1close #123
If the pull request links an issue but does not close it, you can use the keyword ref
like this:
1ref #456
Multiple issues should use full syntax for each issue and separate by a comma, like:
1close #123, ref #456