Skip to content

Latest commit

 

History

History
55 lines (37 loc) · 2 KB

CONTRIBUTING.md

File metadata and controls

55 lines (37 loc) · 2 KB
Raw

Contributing to a brick

Thanks for taking the time to contribute! 🧱🚀

The following is a set of guidelines for contributing. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

Proposing a Change

If you intend to change the public API, or make any non-trivial changes to the implementation, we recommend filing an issue. This lets us reach an agreement on your proposal before you put significant effort into it.

If you’re only fixing a bug, it’s fine to submit a pull request right away but we still recommend to file an issue detailing what you’re fixing. This is helpful in case we don’t accept that specific fix but want to keep track of the issue.

Creating a Pull Request

Before creating a pull request please:

  1. Fork the repository and create your branch from master.
  2. Install all dependencies (flutter packages get or pub get).
  3. Squash your commits and ensure you have a meaningful commit message.
  4. If you've changed the public API, make sure to update/add documentation.
  5. Create the Pull Request.
  6. Verify that all status checks are passing.

While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.

Adding an example

Examples live in the examples folder.

  • For a new brick example, add it to the brickname folder in examples.
  • Any changes you make to a brick will have to be updated in the example folder.

Getting in Touch

If you want to just ask a question or get feedback on an idea you can send me a message Discord.

Code of conduct

Code of conduct

License

By contributing to Bricks, you agree that your contributions will be licensed under its MIT license.