Adds a GPG key to the authenticated user's GitHub account. OAuth app tokens
and personal access tokens (classic) need the `write:gpg_key` scope to use
this endpoint.
Removes a GPG key from the authenticated user's GitHub account. OAuth app
tokens and personal access tokens (classic) need the `admin:gpg_key` scope
to use this endpoint.
Lists the public SSH keys for the authenticated user's GitHub account. OAuth
app tokens and personal access tokens (classic) need the `read:public_key`
scope to use this endpoint.
CREATE A PUBLIC SSH KEY FOR THE AUTHENTICATED USER
Adds a public SSH key to the authenticated user's GitHub account. OAuth
app tokens and personal access tokens (classic) need the `write:gpg_key`
scope to use this endpoint.
View extended details for a single public SSH key. OAuth app tokens and
personal access tokens (classic) need the `read:public_key` scope to use
this endpoint.
DELETE A PUBLIC SSH KEY FOR THE AUTHENTICATED USER
Removes a public SSH key from the authenticated user's GitHub account. OAuth
app tokens and personal access tokens (classic) need the `admin:public_key`
scope to use this endpoint.
LIST PUBLIC EMAIL ADDRESSES FOR THE AUTHENTICATED USER
This text guides on setting the visibility of a user's email address via
the specified GitHub endpoint. It mentions that OAuth app tokens and personal
access tokens require the `user:email` sc
Add one or more social accounts to the authenticated user's profile. OAuth
app tokens and personal access tokens (classic) need the `user` scope to
use this endpoint.
LIST APP INSTALLATIONS ACCESSIBLE TO THE USER ACCESS TOKEN
This GitHub App feature lets authenticated users view installations they
have permissions (:read, :write, or :admin) for, including personal, collaborator,
and organization repositories, detai
LIST REPOSITORIES ACCESSIBLE TO THE USER ACCESS TOKEN
Auth users can access repos they own, collaborate on, or are in their org
with permissions (`:read`, `:write`, `:admin`) detailed under `permissions`
key for an installation.
Remove a single repository from an installation. The authenticated user
must have admin access to the repository. The installation must have the
`repository_selection` of `selected`.
SET INTERACTION RESTRICTIONS FOR YOUR PUBLIC REPOSITORIES
Temporarily restricts which type of GitHub user can interact with your public
repositories. Setting the interaction limit at the user level will overwrite
any interaction limits that are set f
LIST USER ACCOUNT ISSUES ASSIGNED TO THE AUTHENTICATED USER
GitHub's REST API shows issues and pull requests assigned to the user across
owned/member repos. Pull requests are identified with a `pull_request` key.
Use "List pull requests" for PR ids. Su
GET AN ORGANIZATION MEMBERSHIP FOR THE AUTHENTICATED USER
This endpoint returns the membership status of an authenticated user in
an organization unless the user is unaffiliated or the request is from a
blocked GitHub App, resulting in a `404` or `40
This API displays organizations for authenticated users, needing `user`
or `read:org` scope. It limits visibility to organizations the user can
operate on, rejecting inadequate scope with a `4
This text describes the process of fetching a user migration, detailing
the possible states: `pending`, `exporting`, `exported`, and `failed`. It
notes that a successful (exported) migration a
The URL downloads a migration archive (tar.gz) with data (e.g., issues,
pull requests, comments) and directories for attachments and repositories'
Git data.
Migration archives are automatically deleted after 7 days. Despite this,
migration metadata remains accessible via specific GitHub REST API endpoints
even after archive deletion.
This text explains that you can unlock repositories after a user migration
is complete, allowing their use or deletion. If a repository isn't locked,
trying to unlock it will result in a `404
LIST PACKAGES FOR THE AUTHENTICATED USER S NAMESPACE
This endpoint lists packages owned by the user, requiring `read:packages`
scope, and `repo` scope for certain registry types. See GitHub documentation
for registry-specific permissions.
To access a user-owned package, OAuth and classic tokens need `read:packages`
scope. For certain GitHub Packages, `repo` scope is also necessary. Details
on permissions at GitHub's documentati
Authenticated users can delete their package unless it's public with over
5,000 downloads; then, contact GitHub support. OAuth and classic tokens
need `read:packages` and `delete:packages` sco
Authenticated users can restore deleted packages within 30 days if the namespace
and version are available, provided they have the necessary OAuth or personal
access token scopes, including `r
This endpoint lists versions of a user-owned package, requiring `read:packages`
scope with OAuth or classic tokens. For certain registries, `repo` scope
is also needed. Details on permissions
This endpoint retrieves a specific package version for packages owned by
the authenticated user. It requires `read:packages` scope and, for certain
registries, `repo` scope for access, based o
DELETE A PACKAGE VERSION FOR THE AUTHENTICATED USER
Deletes specific package version owned by the user. If public and has >5,000
downloads, contact GitHub support. Requires admin permissions, `read:packages`,
`delete:packages`, and potentially
RESTORE A PACKAGE VERSION FOR THE AUTHENTICATED USER
A user can restore a deleted package version within 30 days if its namespace
and version are unclaimed. OAuth and personal tokens need `read:packages`
and `write:packages` scopes, plus `repo`
Creates a user project board. Returns a `410 Gone` status if the user does
not have existing classic projects. If you do not have sufficient privileges
to perform this action, a `401 Unauthori
This text guides on setting the visibility of a user's email address via
the specified GitHub endpoint. It mentions that OAuth app tokens and personal
access tokens require the `user:email` sc
The text outlines that the authenticated user can access repositories they
own, collaborate on, or are part of through an organization, given explicit
`:read`, `:write`, or `:admin` permission
Creates a new repository for the authenticated user. OAuth app tokens and
personal access tokens (classic) need the `public_repo` or `repo` scope
to create a public repository, and `repo` scop
The text outlines that the authenticated user can access repositories they
own, collaborate on, or are part of through an organization, given explicit
`:read`, `:write`, or `:admin` permission
Creates a new repository for the authenticated user. OAuth app tokens and
personal access tokens (classic) need the `public_repo` or `repo` scope
to create a public repository, and `repo` scop
Authenticated users can delete a repository invitation by invitation ID.
If declined, it returns 204, and for conflicts/errors such as 404 or 403,
see GitHub Docs.
Composio.dev is a platform for building AI applications, designed to make the process of developing AI solutions super easy and fun! It provides a comprehensive set of tools and libraries that simplify the process of developing AI solutions, allowing you to focus on the creative aspects of your project without getting bogged down by the technical details.
How does Composio.dev support github?
Composio.dev seamlessly integrates with github, allowing you to leverage its capabilities within the Composio.dev platform. You can utilize github to call functions across various platforms, including Google, GitHub, and others, making it a breeze to incorporate different services into your AI applications. Additionally, it supports user authentication via OAuth2 and can work in conjunction with other popular frameworks like LangChain and CrewAI, giving you the flexibility to build truly innovative AI solutions.
What models can I use with github?
With github, you have access to a wide range of state-of-the-art language models, including GPT-4o (OpenAI), GPT-3.5 (OpenAI), GPT-4 (OpenAI), Claude (Anthropic), PaLM (Google), LLaMA and LLaMA 2 (Meta), Gemini, and many others. This flexibility allows you to choose the model that best suits your specific use case, whether you're building a chatbot, a content creation tool, or any other AI-powered application. You can experiment with different models and find the one that delivers the best performance for your project.
How can I integrate github into my project?
Composio.dev provides a seamless integration for github, making it super easy to incorporate this powerful framework into your projects. You can leverage the Composio.dev API to call functions from github, allowing you to tap into its capabilities with just a few lines of code. The SDK is available in Python, JavaScript, and TypeScript, so you can work with your preferred programming language and integrate github into your projects seamlessly.
What is the pricing for github?
github is completely free to use, with a generous free tier that allows up to 1000 requests per month. This makes it accessible for developers and organizations of all sizes to explore and experiment with this powerful tool without any upfront costs. Whether you're a student working on a personal project or a startup building the next big thing, you can get started with github without worrying about breaking the bank.
What kind of authentication is supported for github?
github supports OAuth2 authentication, ensuring secure and authorized access to its functionalities. You can leverage the Composio.dev API to handle authentication and call functions from github seamlessly. The SDK is available in Python, JavaScript, and TypeScript for your convenience, making it easy to integrate authentication into your projects and keep your users' data safe and secure.
Can I add github to my project?
Absolutely! You can easily incorporate github into your project by utilizing the Composio.dev API. This API allows you to call functions from github, enabling you to leverage its capabilities within your application. The SDK is available in Python, JavaScript, and TypeScript to facilitate integration, so you can work with the language you're most comfortable with and add github to your project with ease.
What is the accuracy of github?
github is designed to provide highly accurate and reliable results, ensuring that your AI applications perform at their best. The integration with Composio.dev ensures precise function calls, enabling you to build robust and powerful AI applications with confidence. github's comprehensive framework and the ability to leverage state-of-the-art models ensure reliable and accurate outcomes for your AI development needs, whether you're working on a chatbot, a content creation tool, or any other AI-powered project.
What are some common use cases for github?
github can be used for a wide range of AI applications, making it a versatile tool for developers and creators alike. Some common use cases include natural language processing, text generation, question answering, sentiment analysis, and more. It's particularly useful for building chatbots, virtual assistants, content creation tools, and other AI-powered applications that can help you automate tasks, engage with users, and create compelling content. Whether you're working on a personal project or building a product for your startup, github can help you bring your ideas to life.
How does github handle data privacy and security?
Data privacy and security are crucial considerations when working with AI systems, and github takes these issues seriously. It follows industry best practices and adheres to strict data protection regulations, ensuring that your data is kept safe and secure. github provides robust security measures, such as encryption and access controls, to ensure the confidentiality and integrity of your data. You can rest assured that your sensitive information is protected when using github for your AI development needs.
All the tools your AI agents need, in one place.
Composio is an tool set for AI Agents and LLMS, designed to streamline and optimize the connection and interaction with your AI Agents/LLMs.