# Github Verification

## Personal Verification

To verify Github, enter your handle into the Github field of your NFD (see [Setting Metadata](/platform/manage/setting-metadata-records.md)) & update it.&#x20;

Once the field is updated, you will see a 'verify' option show up in the Verification tab, as well as in the Metadata tab below the Github field.&#x20;

<figure><img src="/files/txHVLu0h7RNL6zhLqHaG" alt=""><figcaption><p>Metadata Tab</p></figcaption></figure>

<figure><img src="/files/YQGFcfOnTYmjPsukwJdl" alt=""><figcaption><p>Verification Tab</p></figcaption></figure>

When you click verify, you'll see a dialog to 'start verification'.  Click that.  You'll next see a modal like this:

<figure><img src="/files/QSmIlpyjPLnr0Ue6dwE4" alt=""><figcaption></figcaption></figure>

Follow the directions, creating a **PUBLIC** gist for your user with the contents as specified.  Once completed, come back to the NFD page and click Confirm. &#x20;

If your handle is an organization, do NOT create a gist but follow the changes below.

***

## Organization Verification

Follow the directions above but instead of creating a gist, set the nfd-verify:xxx challenge value into a root file called "**.nfd**" in the **.github** Organization Repo for your organization.

If you don't already have a .github repo, one easy way of doing it is to click the 'create readme' link on the right of your organizations github profile page.  You can also  click the '+' dropdown menu and click New Repository - naming it .github.

<figure><img src="/files/ySDQSFG9Mp5cwoyzBPzA" alt=""><figcaption><p>Clicking 'create a README file' will create your .github repo</p></figcaption></figure>

If you choose the 'New Repository' route.  Here is an example - **notice it must be public** !

<figure><img src="/files/ItEetI1H79ECJ0J8NOeU" alt=""><figcaption><p>Add new .github repo to Organization</p></figcaption></figure>

If you create the empty .github repo like above, then click the 'creating a new file' link.

<figure><img src="/files/TwnEXXnByPkpvxETXBoC" alt=""><figcaption></figcaption></figure>

followed by naming the file '.nfd' and pasting in the challenge:

<figure><img src="/files/BZ85DKg2SU2ahCRLZwTQ" alt=""><figcaption></figcaption></figure>

Commit the changes and then switch back to the NFD page and click Confirm.

***


---

# 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.nf.domains/platform/manage/setting-metadata-records/github-verification.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.
