Skip to content

Latest commit

 

History

History
71 lines (45 loc) · 4.59 KB

CONTRIBUTING.md

File metadata and controls

71 lines (45 loc) · 4.59 KB
Raw

Welcome to FlipperZero contributing guide

Thank you for investing your time in contributing to our project!

Read our Code of Coduct to keep our community approachable and respectable.

In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

New contributor guide

See the ReadMe to get an overview of the project. Here are some helpful resources to get you comfortable with open source contribution:

Getting started

Before writing code and creating PR make sure that it aligns with our mission and guidlines:

  • All our devices are intended for research and education.
  • PR that contains code intended to commit crimes is not going to be accepted.
  • Your PR must contain code compatiable with project LICENSE.
  • PR will only be merged if it pass CI/CD.
  • PR will only be merged if it pass review by code owner.

Feel free to ask questions in issues if you're not sure.

Issues

Create a new issue

If you found a problem, search if an issue already exists. If a related issue doesn't exist, you can open a new issue using a relevant issue form.

Solve an issue

Scan through our existing issues to find one that interests you.

Make Changes

  1. Fork the repository.

  1. Install build requirements

  2. Create a working branch and start with your changes!

Commit your update

Commit the changes once you are happy with them. Make sure that code compilation is not broken and passes tests. Check syntax and formatting.

Pull Request

When you're done making the changes, open a pull request, often referred to as a PR.

  • Fill out the "Ready for review" template so we can review your PR. This template helps reviewers understand your changes and the purpose of your pull request.
  • Don't forget to link PR to issue if you are solving one.
  • Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a Docs team member will review your proposal. We may ask questions or request for additional information.
  • We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
  • As you update your PR and apply changes, mark each conversation as resolved.
  • If you run into any merge issues, checkout this git tutorial to help you resolve merge conflicts and other issues.

Your PR is merged!

Congratulations 🎉🎉 The FlipperDevices team thanks you ✨.