Skip to content

Latest commit

 

History

History
40 lines (31 loc) · 1.75 KB

CONTRIBUTING.md

File metadata and controls

40 lines (31 loc) · 1.75 KB

Contributing to attention-mechanisms

We love your input! We want to make contributing to this project 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

All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). 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 anything, update the corresponding documentation in README.md and code files as well.
  4. Make sure your code is error-free!
  5. Issue that pull request!

Report Bugs using Github's Issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Detailed Bug Reports

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)

Consistent Coding Style

Kindly refer to PEP-8.

License

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

References

I adapted this document from Brian A. Danielak, and he adapted it from the open-source contribution guidelines for Facebook's Draft