# Add GitHub Registry

**Step 1:** Open Registries on the left and click ‘Add’ on the top right.

**Step 2:** Enter your registry’s name and select an icon.

{% hint style="success" %}
**Tip:** You can write a description, so others on your team can understand what’s the purpose of this registry.
{% endhint %}

**Step 3:** Select GitHub Registry type.

![](/files/zUzvSO8lxRg9JtC6DYa8)

**Step 4:** Select if you'd like to add an organization or a user.

**Step 5:** In the corresponding fields, enter:

* Your GitHub user name,
* Personal access token generated in GitHub with the steps documented [**here**](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). Select the `repo` and `read:packages` scopes. `Repo` scope is required due to GitHub's limitations. You're still able to add public GitHub registries, too.
* And your organization’s or your user's GitHub name.

{% hint style="danger" %}
Only classic tokens are supported. Fine-grained tokens aren't supported yet.
{% endhint %}

**Step 6:** Click ‘Save’ button on the top right.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dyrector.io/tutorials/add-your-registry/add-github-registry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.