axolotl/.github/CONTRIBUTING.md

Contributing to axolotl

First of all, thank you for your interest in contributing to axolotl! We appreciate the time and effort you're willing to invest in making our project better. This document provides guidelines and information to make the contribution process as smooth as possible.

Table of Contents

• Code of Conduct
• Getting Started
• How to Contribute
  • Reporting Bugs
  • Suggesting Enhancements
  • Submitting Pull Requests
• Style Guidelines
  • Code Style
  • Commit Messages
• Additional Resources

Code of Conduct

All contributors are expected to adhere to our Code of Conduct. Please read it before participating in the axolotl community.

Getting Started

Bugs? Please check for open issue else create a new Issue.

PRs are greatly welcome!

1. Fork the repository and clone it to your local machine.
2. Set up the development environment by following the instructions in the README.md file.
3. Explore the codebase, run tests, and verify that everything works as expected.

Please run below to setup env

# Install axolotl + dev and test dependencies from lockfile
export UV_TORCH_BACKEND=cu128  # or cu130
uv sync --extra flash-attn --extra deepspeed --group dev --group test
source .venv/bin/activate
pre-commit install

# test
pytest tests/

How to Contribute

Reporting Bugs

If you encounter a bug or issue while using axolotl, please open a new issue on the GitHub Issues page. Provide a clear and concise description of the problem, steps to reproduce it, and any relevant error messages or logs.

Suggesting Enhancements

We welcome ideas for improvements and new features. To suggest an enhancement, open a new issue on the GitHub Issues page. Describe the enhancement in detail, explain the use case, and outline the benefits it would bring to the project.

Submitting Pull Requests

1. Create a new branch for your feature or bugfix. Use a descriptive name like feature/your-feature-name or fix/your-bugfix-name.
2. Make your changes, following the Style Guidelines below.
3. Test your changes and ensure that they don't introduce new issues or break existing functionality.
4. Commit your changes, following the commit message guidelines.
5. Push your branch to your fork on GitHub.
6. Open a new pull request against the main branch of the axolotl repository. Include a clear and concise description of your changes, referencing any related issues.

Skipping CI Checks

You can skip certain CI checks by including specific keywords in your commit messages:

• [skip ci] or skip ci - Skips all CI checks for that commit
• [skip-e2e] or skip-e2e - Skips only end-to-end tests while running other CI checks. You may also include this in the title of your PR to disable end-to-end tests for the entire PR.

Style Guidelines

Code Style

axolotl uses Ruff as its code style guide. Please ensure that your code follows these guidelines.

Use the pre-commit linter to ensure that your code is formatted consistently.

pre-commit run --all-files

Commit Messages

Write clear and concise commit messages that briefly describe the changes made in each commit. Use the imperative mood and start with a capitalized verb, e.g., "Add new feature" or "Fix bug in function".

Additional Resources

• GitHub Help
• GitHub Pull Request Documentation
• Ruff

Thank you once again for your interest in contributing to axolotl. We look forward to collaborating with you and creating an even better project together!