Skip to content

Latest commit

 

History

History
35 lines (18 loc) · 2.03 KB

CONTRIBUTING.md

File metadata and controls

35 lines (18 loc) · 2.03 KB

Contributing to go-chrome

Thank you for taking the time to contribute!

The following is a set of guidelines for contributing to go-chrome and its packages on GitHub. Feel free to propose changes to this document in a pull request.

Contributor agreement

By contributing code and feedback to this project, you agree to abide by the terms of the MPLv2 LICENSE.

Code of conduct

Don't be an ass. If you get called out for being an ass, please just stop being an ass and let it go. If I'm being an ass, call me out and I'll also try to knock it off. Nobody is perfect. I'll be a very sad panda if I ever have to add to this section.

To that end, you hereby agree to abide by the contributor covenant.

Contributing

In order to contribute, simply open an issue or create a pull request.

Report bugs

Please be as detailed as you can when opening an issue to report a bug. An issue template is provided when a new issue is created to help with what I need to troubleshoot a problem. If you have a suggestion for how to resolve the issue please include that as well (or better yet, open a pull request).

Suggest enhancements

To suggest an enhancement please start a discussion by opening a new issue and, as best you can, clearly describe any changes you would like to see and what benefit they give you or the API as a whole. All suggestions of any kind are welcome!

Pull requests

Please feel free to contribute to the project by submitting a pull request. Pull requests can include anything from documentation updates, markdown updates, example code, API changes, bug fixes, etc. Any contributions are welcome!

Styleguide

Submitted go code should be formatted using gofmt or similar (goimports is great).