Skip to content

Latest commit

 

History

History
73 lines (55 loc) · 3.55 KB

CONTRIBUTING.md

File metadata and controls

73 lines (55 loc) · 3.55 KB
Raw

Contributing to Ivoox script

👍🎉 It seems you would like to contribute to the Ivoox script for Nuvola Player. Great to have you here. Here are a few ways you can help make this script better! 🎉👍

Support & Bug Reporting

Whenever you encounter a bug in Nuvola Player, don't hesitate to report it. First of all, it is necessary to submit your issue to the right place.

Tiliado.eu Website

If you have trouble with with Tiliado.eu website (tiliado.eu domain), your Tiliado account and memberships, contact Tiliado support.

Tiliado Repositories

If you have trouble with Tiliado Repositories, Tiliado Repository Installer and installation of Nuvola Player from Tiliado Repositories, report your issue at Tiliado Repositories bug tracker.

Nuvola Player and Streaming Services

If you have any issue with the Nuvola Player application and supported streaming services,

  1. Check the List of Known Issues first.
  2. Take a brief look at Nuvola Player documentation as it might be helpful.
  3. Finally, follow the Bug Reporting Guidelines to create a new bug report.

Development & Hacking

If you would like to contribute some code to this repository, welcome aboard and read on! 👍

Documentation

Developers without commit access to this repository

  • Clone/fork the master branch via GitHub or git clone.
  • Don't work on the master branch directly, but create a feature/topic/devel branch via git checkout -b branch-name. Use meaningful branch name.
  • Make your commits and follow guidelines for commit messages.
  • Push your feature branch to GitHub.
  • Create a pull request following guidelines for pull requests.

Developers with commit access to this repository

  • Keep the master branch clean and functional, because it's the stable/production/release branch.
  • For one-commit changes without a need of code review, work directly on the master branch. Follow guidelines for commit messages.
  • For large changes, use feature/topic/devel branches. You can experiment and break things in these branches, but they must be stable and functional when they are about to be merged back to master. Follow guidelines for commit messages.
  • Create a GitHub pull request following guidelines for pull requests if you would like to have a code review (preferred). Otherwise, feel free to perform a merge on your own following guidelines for merge commits.