Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
93 lines (63 loc) · 3.27 KB

CONTRIBUTING.md

File metadata and controls

93 lines (63 loc) · 3.27 KB
Raw

Contributing to BioNeMo Agent Toolkit

Thank you for your interest in contributing to the BioNeMo Agent Toolkit. We welcome bug reports, feature requests, and pull requests from the community.

How to Contribute

Reporting Issues

  • Search existing issues before opening a new one.
  • Include a clear description, steps to reproduce, and any relevant context.

Submitting a Pull Request

  1. Read the README to understand the repo structure and skill format.
  2. Fork the repository and create your branch from main.
  3. Make your changes, following the existing skill and file conventions.
  4. Ensure your commits are signed off (see Signing Your Work below).
  5. Open a pull request against main with a clear description of the change and its motivation.
  6. Address any review feedback. A maintainer will merge once approved.

Branch Naming

Use a short descriptive prefix followed by a slug:

feat/boltz2-multi-chain-support
fix/diffdock-nim-timeout
docs/improve-workflow-readme

Signing Your Work

All contributors must sign off on their commits. This certifies that the contribution is your original work, or that you have the right to submit it under the same license or a compatible one.

Any contribution containing unsigned commits will not be accepted.

To sign off, use the --signoff (or -s) flag when committing:

git commit -s -m "Add cool feature."

This appends the following line to your commit message:

Signed-off-by: Your Name <your@email.com>

Developer Certificate of Origin

By signing off your commits you agree to the following:

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Full text available at https://developercertificate.org.

License

By contributing, you agree that your contributions will be dual-licensed under the terms described in the LICENSE file (Apache-2.0 OR CC-BY-4.0).