Contributions are what makes the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
- Before submitting a new issue or PR, check if it already exists in issues or PRs.
- If there isn't an issue please create one before any development begins
- GitHub issues: take note of the
needs-approval
label.- For Contributors:
- Feature Requests / Refactoring on a Large Scale: Wait for an Unkey member to approve and remove the
needs-approval
label before you start coding or submitting a PR. - Bugs, Security, Documentation, etc.: You can start coding immediately, even if the
needs-approval
label is present. This label mainly concerns feature requests.
- Feature Requests / Refactoring on a Large Scale: Wait for an Unkey member to approve and remove the
- Our Process:
- Issues from anyone not on the Unkey team automatically receive the
needs-approval
label. - We greatly value new feature ideas. To ensure consistency in the product's direction, they undergo review and approval.
- Issues from anyone not on the Unkey team automatically receive the
- For Contributors:
The development branch is main
. This is the branch that all pull
requests should be made against.
To develop locally:
-
Fork this repository to your own GitHub account and then clone it to your local device.
-
Create a new branch:
git switch -c MY_BRANCH_NAME
-
Follow our getting started guide in our documentation
You can build the project with:
pnpm build
To check the formatting of your code:
pnpm fmt
If you get errors, be sure to fix them before committing.
- Be sure to check the "Allow edits from maintainers" option while creating your PR.
- If your PR refers to or fixes an issue, be sure to add
refs #XXX
orfixes #XXX
to the PR description. ReplacingXXX
with the respective issue number. See more about Linking a pull request to an issue. - Be sure to fill the PR Template accordingly.