Chat with GitHub and automate it — accept a repository invitation in GitHub, on demand or on a schedule. One-click connect, then use it across web, WhatsApp, Telegram, Instagram, Messenger and LINE.
Developer Tools
GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features.
From any chat
100+ GitHub actions, run in plain language from the web or any messaging app — WhatsApp, Instagram, Telegram, Messenger or LINE. Just ask; Mira maps it to the right action and runs it on your account.
Accepts a pending repository invitation that has been issued to the authenticated user.
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for...
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents...
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones de...
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Grants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
Adds a github user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no...
Grants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Adds a specified github user as a collaborator to an existing organization project with a given permission level.
Adds a repository to an existing organization-level github actions secret that is configured for 'selected' repository access.
Grants an existing repository access to an existing organization-level dependabot secret; the repository must belong to the organization, and the call succeeds without change if...
Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
Grants a repository access to an organization-level github actions variable, if that variable's visibility is set to 'selected repositories'.
Adds one or more social media links (which must be valid, full urls for platforms supported by github) to the authenticated user's public github profile.
Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.
Overwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.
Sets/replaces list of users allowed to push to a protected branch; usernames (e.g., `["user1"]`) must be a json array in request body (not schema parameters), an empty array `[]...
Sets or replaces the list of organization members granted codespaces access billed to the organization; ensure the organization's billing settings allow access for selected memb...
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Assigns an existing organization-level role (identified by `role id`) to a team (identified by `team slug`) within a github organization (`org`), provided the organization, team...
Assigns a specific organization role to a user who is a member or an outside collaborator in a github organization, using a valid role id.
Lists docker packages for the authenticated user that encountered conflicts during the docker migration process.
Blocks an existing individual github user (not an organization or your own account), preventing them from interacting with your account and repositories.
Blocks an existing github user from an existing organization, preventing their contributions, collaboration, and forking of the organization's repositories.
Cancels an existing, ongoing or queued github pages deployment for a repository using its `pages deployment id`.
Cancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').
Checks if a github app or oauth access token is valid for the specified client id and retrieves its details, typically to verify its active status and grants.
Checks if a gist, identified by `gist id`, is starred by the authenticated user, returning an empty response (204) if starred, or a 404 error if not starred or not found.
Checks if the authenticated github user follows a target github user; an http 204 status indicates the user is followed, while an http 404 status indicates the user is not follo...
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response d...
Verifies if a github user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the r...
Checks if a specified github user can be assigned to a given issue within a repository.
Checks if a github user `username` follows `target user`; returns a 204 http status if true, 404 if not or if users are invalid.
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Checks if a github user is blocked by an organization; a successful response (204 no content) indicates the user is blocked, while a 404 not found error indicates the user is no...
Checks if the specified github user is blocked by the authenticated user; a 204 no content response indicates the user is blocked, while a 404 not found indicates they are not.
Checks if private vulnerability reporting is enabled for the specified repository.
Checks if a team has 'read', 'write', or 'admin' permissions for an organization's specific classic project, returning the project's details if access is confirmed.
Checks a team's permissions for a specific repository within an organization, including permissions inherited from parent teams.
Deletes github actions caches from a repository matching a specific `key` and an optional git `ref`, used to manage storage or clear outdated/corrupted caches; the action succee...
Removes all custom labels from a self-hosted runner for an organization; default labels (e.g., 'self-hosted', 'linux', 'x64') will remain.
Compares two commit points (commits, branches, tags, or shas) within a repository or across forks, using `base...head` or `owner:ref...owner:ref` format for the `basehead` param...
Generates a jit configuration for a github organization's new self-hosted runner to run a single job then unregister; the runner group id must exist.
Sets or updates the oidc subject claim customization template for an existing github organization by specifying which claims (e.g., 'repo', 'actor') form the oidc token's subjec...
Converts an existing organization member, who is not an owner, to an outside collaborator, restricting their access to explicitly granted repositories.
Creates a git blob in a repository, requiring content and encoding ('utf-8' or 'base64').
Creates a new check run for a specific commit in a repository, used by external services to report status, detailed feedback, annotations, and images directly within the github ui.
Creates a new check suite for a specific commit (`head sha`) in an original repository (not a fork); github dispatches a `check suite` webhook event with the `requested` action...
Creates a github codespace for the authenticated user, requiring a json request body with either `repository id` (integer) or a `pull request` object (containing `pull request n...
Creates a github codespace for an open pull request in a codespaces-enabled repository, with options to customize its configuration.
Creates a github codespace for the authenticated user in a specified repository, which must be accessible and use a valid `devcontainer.json` if `devcontainer path` is specified.
Creates a new commit in a github repository; the `tree` sha and any `parents` shas must already exist in the repository.
Creates a comment on a specific commit, or on a specific line if `path` and `position` are provided.
Sets a commit's status (e.g., error, failure, pending, success from ci/cd) for a given sha; max 1000 statuses per sha/context.
Creates a custom role with defined permissions within a github organization.
Creates a deploy key for a repository; the repository must exist and be accessible, and the provided key must be a valid public ssh key.
Creates a github deployment for an existing repository, targeting a specific ref (branch, tag, or sha) that must also exist within the repository.
Creates a deployment branch or tag policy for an existing environment in a github repository, using a ruby file.fnmatch pattern (where `*` doesn't match `/`) to specify which br...
Creates a status for an existing deployment, updating its operational state, associated urls, and description.
Creates a new discussion post on a specific team's page within an organization.
Creates a new comment on an existing team discussion within a github organization.
Creates a fork of an accessible repository, optionally into a specific organization, with a new name, or copying only the default branch.
Creates a new gist on github with provided files, an optional description, and public/secret visibility.
Creates a new comment on a specified github gist.
Use this action to finalize a github app's creation by exchanging the temporary `code` (received as a url parameter during the app manifest setup redirection) for the app's full...
Creates a github pages deployment for a repository using a specified artifact and oidc token, provided github pages is enabled and the artifact (containing static assets) is acc...
Configures or updates github pages for a repository, setting build type and source; ensure a pages workflow exists for 'workflow' `build type`, or `source branch` exists for 'le...
Creates a new label in a specified github repository, provided the repository exists and the user has write permissions.
Creates a milestone in a github repository for tracking progress on issues or pull requests; requires repository existence and user write permissions.
Creates a repository autolink to automatically convert text references (e.g., 'ticket-123') into hyperlinks, using a unique `key prefix` and a `url template` that includes `<num>`.
Creates an encrypted environment variable for a pre-existing environment within a github repository; will fail if the variable name already exists.
Creates a new issue in a github repository, requiring the repository to exist and have issues enabled; specific fields like assignees, milestone, or labels may require push access.
Creates a new comment on an existing github issue or pull request within the specified repository.
Creates a new classic project board within a specified github organization.
Creates a new repository within a specified github organization, with options for detailed configuration including visibility, features, merge strategies, initial commit, and te...
Creates a new, uniquely named github actions variable for an organization, with configurable repository access visibility (all, private, or selected).
Creates a webhook for a github organization to deliver event notifications to a configured url.
Creates a project card in a github project column; the request body must contain either a `note` for a note-only card, or both `content id` (id of an issue or pull request) and...
Creates a new column in a github project (classic).
Creates a pull request in a github repository, requiring existing `base` and `head` branches; `title` or `issue` must be provided.
Creates a git reference (e.g., a branch or tag) in a repository; the repository must not be empty prior to this operation.
Generates a temporary (one-hour) registration token to add a new self-hosted runner to an organization for github actions.
Generates a time-limited token required to register a new self-hosted runner with a specific repository.
Creates a release in a github repository for a specified tag; the tag must be unique for published releases, and if a `discussion category name` is given, it must already exist.
Generates a token, valid for one hour, to authenticate removing a self-hosted runner from an organization.
Generates a temporary (one-hour validity) token required to unregister and remove a self-hosted runner from a repository.
Posts a reply to a specific review comment on a github pull request, requiring the repository, pull request, and original comment to exist, and a non-empty reply body.
Triggers a github actions workflow or a webhook on a repository by creating a repository dispatch event, allowing programmatic triggering of workflows based on events outside of...
Creates a new repository for the authenticated user, optionally within an organization if `team id` is specified.
Publishes the specified codespace to a new repository, using the codespace's current state as the initial commit.
Creates a new classic project board within a specified repository; classic projects must be enabled for the target repository.
Showing the first 100 — GitHub has even more actions. Connect it in chat to browse and run the full set.
Chat or automate
Ask once, or set it and forget it. Turn GitHub actions into recurring vMira workflows — scheduled runs and GitHub event triggers that run on their own and deliver straight to your chat on any platform.
Mira accept a repository invitation and sends the result to your chat.
Mira kicks off a workflow automatically — GitHub ships 46 event triggers.
Mira chains several GitHub actions into one recurring workflow, delivered wherever you chat.
Try asking
“Accept a repository invitation in GitHub”
“List repositories starred by the authenticated user in GitHub”
“List stargazers in GitHub”
“Star a repository for the authenticated user in GitHub”
“Add email for auth user in GitHub”
One minute to connect
01
On the web app or in WhatsApp, Telegram, Instagram or Messenger.
02
Tell Mira what you want done — e.g. “Accept a repository invitation in GitHub.”
03
Mira opens a secure, least-privilege link to GitHub. Approve it once; revoke anytime in settings.
FAQ
Yes. Connect GitHub to vMira and run it from any chat in one click. Mira turns your plain-language request into the right GitHub action and runs it on your account.
100+ GitHub actions — including Accept a repository invitation, List repositories starred by the authenticated user, List stargazers. Just ask in plain language once it is connected.
Yes. Beyond one-off asks, build recurring vMira workflows — scheduled runs and GitHub event triggers that chain GitHub actions and deliver the result to your chat automatically.
The web at vmira.ai and inside WhatsApp, Instagram, Telegram, Messenger and LINE — one account, with your history and connected apps following you across every surface.
You can start free. Paid plans (from $4/mo) raise the limits and unlock heavier use, the top models, and more workflow runs. The same account works on the web and every messaging app.
Related
Every AI. Up to 200× the usage. From $4 a month.