Skip to content

Latest commit

 

History

History
47 lines (33 loc) · 1.69 KB

CONTRIBUTING.md

File metadata and controls

47 lines (33 loc) · 1.69 KB
Raw

rules_pkl Contributors Guide

Welcome to the Pkl community, and thank you for contributing! This guide explains how to get involved.

Licensing

rules_pkl is released under the Apache 2.0 license. This is why we require that, by submitting a pull request, you acknowledge that you have the right to license your contribution to Apple and the community, and agree that your contribution is licensed under the Apache 2.0 license.

Issue Tracking

To file a bug or feature request, use GitHub Issues. Be sure to include the following information:

  • Context
    • What are/were you trying to achieve?
    • What's the impact of this bug/feature?

For bug reports, additionally include the following information:

  • The complete error message.
  • The simplest possible steps to reproduce.
  • Version information of pkl, bazel, and any other mentioned tools/systems.
  • Error messages from the target system.

Pull Requests

When preparing a pull request, follow this checklist:

  • Imitate the conventions of surrounding code.
  • Follow the seven rules of great Git commit messages:
    • Separate subject from body with a blank line.
    • Limit the subject line to 50 characters.
    • Capitalize the subject line.
    • Do not end the subject line with a period.
    • Use the imperative mood in the subject line.
    • Wrap the body at 72 characters.
    • Use the body to explain what and why vs. how.

Maintainers

The project’s maintainers (those with write access to the upstream repository) are listed in MAINTAINERS.md.