Skip to content

Contributing to Jentic Projects

Thank you for considering contributing to Jentic's open source projects!
Our ecosystem includes:

This guide covers contributing to any Jentic project. For project-specific contribution rules, see each repository's README or CONTRIBUTING.md.

Code of Conduct

We are committed to a welcoming and inclusive environment.
Please read our Code of Conduct before contributing.

Ways to Contribute

Contributions aren’t just code — you can help by:

  • Reporting bugs
  • Suggesting features
  • Reviewing pull requests
  • Improving documentation
  • Sharing tutorials, guides, and examples
  • Helping others in the Discord community

How to Get Started

  1. Find or Create an Issue
    Search the repository's GitHub Issues first. If none exists, open one.

  2. Discuss Before Large Changes
    For new features or large refactors, open an issue first to get feedback.

  3. Fork and Branch

  4. Feature branches: feature/<short-description>

  5. Bugfix branches: fix/<issue-number>-<short-description>

  6. Code and Test
    Follow the coding guidelines in this doc and project-specific rules.

  7. Submit a Pull Request

  8. Keep PRs focused and small
  9. Describe what and why you changed
  10. Link related issues (Fixes #123)

Coding Guidelines

  • Commits: Follow Conventional Commits
  • Style: Match the project’s existing formatting and linting rules
  • Tests: Add or update tests where applicable
  • Docs: Update docs for new features or changes

Project-Specific Notes

Jentic Public APIs

See Add API Integration and Create Agent Workflows for contributing OpenAPI specs and workflows.

Arazzo Engine

Follow the development guide.

Standard Agent

Check the reference docs for architecture and runtime components before contributing.

Recognition

We credit contributors in release notes and documentation.
Thank you for helping build the Jentic ecosystem!