> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets/github-assets.md). # GitHub assets You can use using different [filtering options](#filter-options) to view GitHub assets for specific [use cases](#use-cases), such as specific language or visibility.

Data for GitHub assets is displayed according to these columns:

GitHub column	Description
Name	Clicking the asset name opens the asset in GitHub
Visibility	Private, public, internal, private template, public template
Language	Code language. For example, JavaScript, TypeScript, Python
Open issues	Number of open issues in GitHub asset
Last updated	Date asset was most recently updated

## Filter options Filter options for GitHub assets include the following:

Filter	Comparator	Description
Name	String	Name of GitHub asset: Equals, doesn't equal, starts with, ends with, contains, doesn't contain
Visibility	Includes, excludes	Exposure of GitHub asset: Private, public, internal, private template, public template
Language	String	Programming language: Equals, doesn't equal, starts with, ends with, contains, doesn't contain
Last updated	Date	Date that GitHub asset was updated: Equals, after, before, is between
Repository ID	String	Unique GitHub repository identifier: Equals, doesn't equal, starts with, ends with, contains, doesn't contain

## Use cases A common use case filtering example for GitHub includes new applications and repos in GitHub that have publicly visible assets: `Visibility includes public, public template`

--- # 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.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets/github-assets.md?ask=&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.