Skip to content

Latest commit

 

History

History
57 lines (39 loc) · 2 KB

CONTRIBUTING.md

File metadata and controls

57 lines (39 loc) · 2 KB
Raw

Contributing to Capco Digital

Capco

Purpose

We love your input! We want to make contributing to these projects as easy and transparent as possible, whether it's:

  • Reporting a bug
  • Discussing the current state of the code
  • Submitting a fix
  • Proposing new features
  • Becoming a maintainer

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

We use Github Flow

We Use Github Flow, All Code Changes Happen Through Pull Requests Pull requests are the best way to propose changes to the codebase.

We actively welcome your pull requests:

  1. Fork the repo and create your branch from master
  2. If you've added code that should be tested, add tests
  3. If you've changed APIs, update the documentation
  4. Ensure the test suite passes
  5. Make sure your code lints
  6. Issue that pull request!

MIT Software License

In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Reporting Bugs via Issues

We use GitHub issues to track public bugs. It's that easy!

Write Bug reports With Detail, Background and Sample Code

Great Bug Reports tend to have:

  • A quick summary and/or background
  • Steps to reproduce
    • Be specific!
    • Give sample code if you can
  • What you expected would happen
  • What actually happens
  • Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love thorough bug reports. I'm not even kidding.

License

By contributing, you agree that your contributions will be licensed under its MIT License.

References

This document was adapted from the open-source contribution guidelines for Facebook's Draft