Skip to content
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.

Latest commit

 

History

History
42 lines (33 loc) · 2.09 KB

CONTRIBUTING.md

File metadata and controls

42 lines (33 loc) · 2.09 KB

Contributing to mxpanel

First off, thanks for taking the time to contribute!

Now, take a moment to be sure your contributions make sense to everyone else. These are just guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Reporting Issues

Found a problem? Want a new feature? First of all see if your issue or idea has already been reported. If don't, just open a new clear and descriptive issue.

Submitting pull requests

Pull requests are the greatest contributions, so be sure they are focused in scope, and do avoid unrelated commits. And submit your pull request after making sure that all tests pass and they are covering 100% of the code.

  • Fork it!
  • Clone your fork: git clone https://github.com/<your-username>/mxpanel
  • Navigate to the newly cloned directory: cd mxpanel
  • Create a new branch for the new feature: git checkout -b my-new-feature
  • Install the tools necessary for development: mix deps.get
  • Make your changes.
  • Commit your changes: git commit -am 'Add some feature'
  • Push to the branch: git push origin my-new-feature
  • Submit a pull request with full remarks documenting your changes.

Publishing new versions

  1. Bump the version on README and mix.exs
  2. Update the changelog
  3. Make a commit for the new version git commit -am "vx.x.x"
  4. Tag the version git tag "vx.x.x" && git push origin main --tags
  5. Publish to hex mix hex.publish
  6. Create a new release