> For the complete documentation index, see [llms.txt](https://docs.guild.xyz/guild/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guild.xyz/guild/how-to-setup-requirements/github.md).

# Github

Verify GitHub activity and account properties to ensure members are active developers or meet specific contribution requirements.

#### Setting up GitHub requirements

**Star a repository:**

* In the role editor, click **"Add requirements"** and go to **GitHub**
* Choose **Star a repository**
* Enter the **Repo ID** of the GitHub repository you want to track
* Check the box if members must have starred the repo, or uncheck if they must NOT have starred it

\
**Account age**

* Choose **Account age**
* Select a date and choose your logic:
  * **On** - Account created exactly on this date
  * **After** - Account created after this date
  * **Before** - Account created before this date
  * **After or on / Before or on** - Account created on or after/before the date

\
**Commit count**

* Choose **Commit count**
* Set the commit count condition using:
  * **Equal** - Exactly this number of commits
  * **Doesn't equal** - Any number except the one specified
  * **Greater than** - More than the specified number
  * **Greater than or equal to** - At least the specified number
  * **Less than** - Fewer than the specified number
  * **Less than or equal to** - At most the specified number

For all requirements, customize the requirement name and image if you want, then click **"Add requirement"**.

Members connect their GitHub account and Guild automatically verifies their activity and account details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guild.xyz/guild/how-to-setup-requirements/github.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.