Skip to content

Latest commit

 

History

History
67 lines (45 loc) · 1.71 KB

File metadata and controls

67 lines (45 loc) · 1.71 KB

Contributing to aief-engino

Thank you for contributing to AI Employee Force. This document outlines our contribution process.

Getting started

  1. Fork the repository
  2. Create a feature branch: git checkout -b feat/your-feature-name
  3. Make your changes
  4. Run tests: npm test (when applicable)
  5. Submit a pull request

Branch naming

Prefix Use for
feat/ New features
fix/ Bug fixes
docs/ Documentation only
chore/ Build, tooling, maintenance
refactor/ Code refactoring
test/ Adding or updating tests

Commit message format

We follow Conventional Commits:

<type>(<scope>): <description>

[optional body]

[optional footer]

Examples:

  • feat(api): add agent status endpoint
  • fix(auth): handle expired token edge case
  • docs: update local development setup

Pull request checklist

Before submitting a PR, ensure:

  • Code follows existing patterns and style
  • Tests are added or updated for changed behaviour
  • Documentation is updated if public API changes
  • PR description explains the why, not just the what
  • The PR is linked to a relevant issue (if one exists)

Code review

  • All PRs require at least one approval from @AI-employee-force/agent-engino-team
  • Address review feedback as commits (do not force-push during review)
  • Resolve all conversations before merging

Issues

Use the issue templates in .github/ISSUE_TEMPLATE/ to report bugs or request features.

Code of Conduct

Be respectful, constructive, and professional. We follow the Contributor Covenant.


Owner team: @AI-employee-force/agent-engino-team