Skip to content

Latest commit

 

History

History
47 lines (33 loc) · 2.5 KB

CONTRIBUTING.md

File metadata and controls

47 lines (33 loc) · 2.5 KB
Raw

Issues

When opening issues, please make sure that you include as much information as applicable.

  • If your issue is an error, include a stacktrace of what went wrong. This can be attached as a file, or uploaded to a GitHub Gist.
  • If your issue is a bug or otherwise unexpected behavior, explain what happened and what you expected to happen.
  • If you're having trouble setting the bot up, we recommend joining our Discord as we will be able to provide more dynamic support there.

Pull Requests

We love to see when people contribute to the project! Our Issues Page often has a list of features that need to be implemented. However, you'll need to read the following guidelines:

Contributor License Agreement (CLA)

By submitting changes to the repository, you are hereby agreeing that:

  • Your contributions will be licensed irrevocably under the GNU General Public License v3.0.
  • Your contributions are of your own work and free of legal restrictions (such as patents and copyrights) or other issues which would pose issues for inclusion or distribution under the above license.

If you do not agree with these terms, please do not submit contributions to this repository. If you have any questions about these terms, feel free to join our Discord and ask any questions that you may have.

Pull Request Policy

This PR policy has been adapted from the Quilt Mappings PR policy

  1. Look at the code style

    Before you begin work on adding code to LilyBot, please spend some time looking through the rest of the code in LilyBot, and ensure in your Pull Request you follow the style as closely as you can.

    If you have any questions, do not hesitate to ask in our Discord.

  2. Open your PR and wait for reviews

    Once you have forked LilyBot and opened a pull request, you will need to wait for reviews from other people. When you get reviews, try to thoughtfully address any concerns other people have. If you get confused, be sure to ask questions!

  3. Merging your PR

    Once your PR has accumulated at least one review by a project member, it will be merged!