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

# Internal workflow

> Internal guidelines for working in the Unkey repository

Unkey is not accepting external pull requests at this time. Pull requests from people outside the Unkey team won't be reviewed or merged. Issues remain open for bug reports, feature requests, and documentation feedback.

This guide is for Unkey team members working in this repository.

## Before you start

Discuss significant work before writing code. Use GitHub Issues, Linear, project docs, or the relevant Slack channel so the team can review context asynchronously.

For bug fixes, documentation updates, and small follow-ups, link the issue or context in the pull request.

## House rules

### Issue and PR guidelines

* Before submitting a new issue or PR, check existing <a href="https://github.com/unkeyed/unkey/issues" target="_blank">issues</a> and <a href="https://github.com/unkeyed/unkey/pulls" target="_blank">PRs</a>.
* Create or link an issue for work that needs tracking.
* Reference the issue in your PR using `fixes #123` or `refs #123`.
* Explain what changed, why it changed, and how you verified it.

### Approval process

Requires prior alignment:

* New features
* Refactoring work
* Changes to core functionality
* UI or UX changes

Can start immediately when scoped:

* Bug fixes
* Security improvements
* Documentation updates
* Typo corrections

## External feedback

Use GitHub Issues for bug reports, feature requests, and documentation feedback. Use <a href="https://unkey.com/discord" target="_blank">Discord</a> for questions and support.

Report security issues by emailing <a href="mailto:security@unkey.com">[security@unkey.com](mailto:security@unkey.com)</a>. Do not open public security issues.