> ## Documentation Index
> Fetch the complete documentation index at: https://phalanetwork.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Contributing to dstack

> It's the easiest way to deploy existing Docker applications to Trusted Execution Environments with hardware-enforced security

## Contributing to dstack

Contributing to dstack goes beyond code—it includes documentation improvements, security research, educational content, and community building. We recognize that expertise comes in many forms, and every contribution strengthens the ecosystem.

To get started, follow these straightforward steps to contribute via GitHub:

#### Fork & Star Repository

* ⭐️ **Star the repository**: [dstack repository](https://github.com/Dstack-TEE/dstack)
* 🍴 **Fork the repository** to your GitHub account.

#### Creating a Pull Request (PR)

1. **Clone the forked repo:**

```bash theme={null}
   git clone https://github.com/YOUR_USERNAME/dstack.git
   cd dstack
```

2. **Create a branch for your changes:**

   ```bash theme={null}
   git checkout -b fix/your-issue-description
   ```

3. **Make your changes** and commit:

   ```bash theme={null}
   git add .
   git commit -m "fix: short description of changes"
   ```

4. **Push your branch**:

   ```bash theme={null}
   git push origin fix/your-issue-description
   ```

5. **Open a PR** on the [dstack repository](https://github.com/Dstack-TEE/dstack) from your branch. Reference the relevant [issue](https://github.com/Dstack-TEE/dstack/issues) clearly in your PR description.

#### PR Template

Use this simple template for your PR description:

```md theme={null}
### Description
Brief summary of the change.

### Related Issue
Link or number of the issue (e.g., closes #123).

### Type of Change
- [ ] Bug fix
- [ ] Enhancement
- [ ] Documentation update

### Additional Context
Any additional information here.
```

#### Creating Issues

* Clearly state the problem or enhancement.
* Label appropriately: `bug`, `enhancement`, or `documentation`.
* Provide steps to reproduce if it's a bug.

**Please allow 1-3 days for responses from core contributors.**