Contributing to ThreadCells

Thanks for helping improve ThreadCells. Reports and pull requests are welcome when they are focused, actionable, and safe to discuss publicly.

Choose the right route

• Bug: use the bug report form with reproduction steps or durable evidence.
• Enhancement: use the feature request form and start with the problem or use case.
• Documentation: use the documentation report form for missing, stale, or unclear public guidance.
• Questions and troubleshooting: check the documentation and Troubleshooting, then ask in Discussions Q&A.
• Early ideas: start with the problem or use case in Discussions Ideas. Move to an Issue only when the outcome is concrete and actionable under the Issue policy.
• Setups and use cases: share workflows, integrations, screenshots, and lessons in Show and tell.
• Security: do not open a public Issue. Follow SECURITY.md and report privately.

Search existing Discussions or open and closed Issues before starting a new thread or report. The detailed Issue eligibility, evidence, triage, and disclosure rules are in the canonical Issue policy.

Pull requests

Before opening a pull request:

1. Start from the latest main and check for overlapping Issues and pull requests.
2. Keep the change bounded; discuss significant work in an Issue first.
3. Add or update focused tests and documentation where behavior changes.
4. Run the relevant local checks and list their outcomes in the pull request.
5. Do not include credentials, private paths, personal data, production state, or terminal transcripts.
6. Use a clear commit message and respond to review and CI feedback.

ThreadCells is an independent technical preview. Keep public collaboration respectful and limited to information that is safe to disclose. See LICENSE for contribution licensing.