Skip to content

Latest commit

 

History

History
72 lines (45 loc) · 3.06 KB

CONTRIBUTING.md

File metadata and controls

72 lines (45 loc) · 3.06 KB
Raw

CONTRIBUTING

Contributions are always welcome, no matter how large or small.

Some thoughts to help you contribute to this project

Recommended Communication Style

  1. Always leave screenshots for visuals changes
  2. Always leave a detailed description in the Pull Request. Leave nothing ambiguous for the reviewer.
  3. Always review your code first. Do this by leaving comments in your coding noting questions, or interesting things for the reviewer.
  4. Always communicate. Whether it is in the issue or the pull request, keeping the lines of communication helps everyone around you.

Setup (forks are preferred).

$ git clone https://github.com/<your-name>/badget
$ cd badget
$ pnpm i

Building

$ pnpm run build

Pull Requests

We actively welcome your pull requests, however linking your work to an existing issue is preferred.

  1. Fork the repo and create your branch
  2. Name your branch something that is descriptive to the work you are doing. i.e. adds-new-thing or fixes-mobile
  3. Make sure you address any lint warnings.
  4. Run pnpm run format if your unsure
  5. If you make the existing code better, please let us know in your PR description.
  6. A PR description and title are required. The title is required to begin with: "feat:" or "fix:"
  7. Link to an issue in the project. Unsolicited code is welcomed, but an issue is required for announce your intentions. PR's without a linked issue will be marked invalid and closed.

note for maintainers: All pull requests need a label to assist automation. See the template to guide which labels to use.

PR Validation

Examples for valid PR titles:

  • fix: Correct typo.
  • feat: Add support for Node 12.
  • refactor!: Drop support for Node 6.

Note that since PR titles only have a single line, you have to use the ! syntax for breaking changes.

See Conventional Commits for more examples.

Work in progress

GitHub has support for draft pull requests, which will disable the merge button until the PR is marked as ready for merge.

Issues

If you plan to contribute a change based on an open issue, please assign yourself by commenting on the following word .take. Issues that are not assigned are assumed open, and to avoid conflicts, please assign yourself before beginning work on any issues.

If you would like to contribute to the project for the first time, please consider joining checking the bug or good first issue labels.

Also, all questions are welcomed.

Community

Do you have questions? Join the conversation in our Discord.

License

Badget is open-source under the GNU Affero General Public License Version 3 (AGPLv3) or any later version.