Contributing¶

StaffOps is a community project. Every contribution matters — from fixing a typo to building a new agent.

Ways to contribute¶

Report an issue¶

Found a bug or something that doesn't work as documented? Open an issue in the relevant repository.

Be specific: what did you expect, what happened, and how to reproduce it.

Improve documentation¶

Docs live inside each repository under docs/. If something is unclear, missing, or wrong — a pull request fixing it is always welcome.

Submit a pull request¶

Fork the repository you want to contribute to
Create a branch (git checkout -b feat/my-contribution)
Make your changes
Run existing tests if available
Open a pull request with a clear description of what and why

One of the most valuable things you can contribute is a real-world operational insight — a pattern that worked, a pitfall to avoid, a decision and its tradeoffs.

Open an issue or a discussion describing it and we'll document it in the project.

Code standards¶

Follow the conventions of the language the project uses
Write tests for new behavior
Keep changes focused — one thing per pull request
Prefer simple, readable code over clever abstractions

Commit conventions¶

We use Conventional Commits:

feat(scope): add new capability
fix(scope): resolve specific bug
docs(scope): update documentation
chore(scope): maintenance task

License¶

By contributing, you agree that your contributions will be licensed under Apache 2.0.

Copyright for all contributions belongs to StaffOps Contributors.

Code of conduct¶

Be respectful. Be constructive. Assume good intent.

We're all here to build something useful together.