Automate GitHub

What GitHub is

GitHub's v3 REST API.

API host: api.github.com

Things people automate with GitHub

• Post new GitHub issues and pull requests to SlackGitHub → Slack
• Post new GitHub issues and pull requests to TelegramGitHub → Telegram
• Post new GitHub issues and pull requests to Google ChatGitHub → Google Chat
• Create an Asana task for every new GitHub issueGitHub → Asana
• Create a Jira task for every new GitHub issueGitHub → Jira
• Create a Google Tasks task for every new GitHub issueGitHub → Google Tasks

What HumDay can do in GitHub

383 documented operations change something in GitHub. The 30 most useful are listed here.

• DELETEDelete an email address for the authenticated user/user/emails
• POSTAdd an email address for the authenticated user/user/emails
• POSTCreate a public SSH key for the authenticated user/user/keys
• POSTCreate a GPG key for the authenticated user/user/gpg_keys
• POSTCreate a SSH signing key for the authenticated user/user/ssh_signing_keys
• PATCHSet primary email visibility for the authenticated user/user/email/visibility
• PATCHUpdate the authenticated user/user
• POSTCreate a gist comment/gists/{gist_id}/comments
• POSTCreate a repository for the authenticated user/user/repos
• POSTCreate a user project/user/projects
• POSTCreate a codespace for the authenticated user/user/codespaces
• POSTCreate an issue/repos/{owner}/{repo}/issues
• POSTCreate a gist/gists
• POSTRender a Markdown document/markdown
• POSTCreate an organization webhook/orgs/{org}/hooks
• DELETEDelete a public SSH key for the authenticated user/user/keys/{key_id}
• DELETEDelete an issue comment/repos/{owner}/{repo}/issues/comments/{comment_id}
• PATCHUpdate an issue comment/repos/{owner}/{repo}/issues/comments/{comment_id}
• POSTCreate an issue comment/repos/{owner}/{repo}/issues/{issue_number}/comments
• DELETEUnblock a user/user/blocks/{username}
• PUTBlock a user/user/blocks/{username}
• DELETEUnfollow a user/user/following/{username}
• PUTFollow a user/user/following/{username}
• DELETEDelete a GPG key for the authenticated user/user/gpg_keys/{gpg_key_id}
• POSTRender a Markdown document in raw mode/markdown/raw
• DELETEDelete an SSH signing key for the authenticated user/user/ssh_signing_keys/{ssh_signing_key_id}
• DELETERemove interaction restrictions from your public repositories/user/interaction-limits
• PUTSet interaction restrictions for your public repositories/user/interaction-limits
• POSTCreate reaction for an issue comment/repos/{owner}/{repo}/issues/comments/{comment_id}/reactions
• PUTCreate or update a secret for the authenticated user/user/codespaces/secrets/{secret_name}

What HumDay can read from GitHub

These are the operations a schedule or a trigger can watch.

• GETList email addresses for the authenticated user/user/emails
• GETList public email addresses for the authenticated user/user/public_emails
• GETList issues assigned to the authenticated user/issues
• GETList events for the authenticated user/users/{username}/events
• GETList events received by the authenticated user/users/{username}/received_events
• GETList public SSH keys for the authenticated user/user/keys
• GETList users blocked by the authenticated user/user/blocks
• GETList user account issues assigned to the authenticated user/user/issues
• GETList GPG keys for the authenticated user/user/gpg_keys
• GETList followers of the authenticated user/user/followers
• GETList the people the authenticated user follows/user/following
• GETList SSH signing keys for the authenticated user/user/ssh_signing_keys
• GETList public events for a user/users/{username}/events/public
• GETList public events received by a user/users/{username}/received_events/public
• GETGet the authenticated user/user
• GETList gists for the authenticated user/gists
• GETList users/users
• GETList public events/events
• GETList organization issues assigned to the authenticated user/orgs/{org}/issues
• GETList notifications for the authenticated user/notifications
• GETList public keys for a user/users/{username}/keys
• GETList organizations for a user/users/{username}/orgs
• GETList gists for a user/users/{username}/gists
• GETList repositories for a user/users/{username}/repos
• GETList repositories starred by a user/users/{username}/starred
• GETList GPG keys for a user/users/{username}/gpg_keys
• GETList packages for a user/users/{username}/packages
• GETList user projects/users/{username}/projects
• GETList followers of a user/users/{username}/followers
• GETList the people a user follows/users/{username}/following
• GETList issue events for a repository/repos/{owner}/{repo}/issues/events
• GETList organization events for the authenticated user/users/{username}/events/orgs/{org}
• GETList repositories watched by a user/users/{username}/subscriptions
• GETList issue comments for a repository/repos/{owner}/{repo}/issues/comments
• GETList SSH signing keys for a user/users/{username}/ssh_signing_keys
• GETList organizations for the authenticated user/user/orgs
• GETList repositories for the authenticated user/user/repos
• GETList teams for the authenticated user/user/teams
• GETSearch users/search/users
• GETList repositories starred by the authenticated user/user/starred
• GETSearch issues and pull requests/search/issues
• GETList packages for the authenticated user's namespace/user/packages
• GETList codespaces for the authenticated user/user/codespaces
• GETList user migrations/user/migrations
• GETList app installations accessible to the user access token/user/installations
• GETList repositories watched by the authenticated user/user/subscriptions
• GETList subscriptions for the authenticated user/user/marketplace_purchases
• GETList repository invitations for the authenticated user/user/repository_invitations
• GETGet a user/users/{username}
• GETList deliveries for an app webhook/app/hook/deliveries
• GETList organization memberships for the authenticated user/user/memberships/orgs
• GETList secrets for the authenticated user/user/codespaces/secrets
• GETGet rate limit status for the authenticated user/rate_limit
• GETGet an issue event/repos/{owner}/{repo}/issues/events/{event_id}
• GETList users blocked by an organization/orgs/{org}/blocks
• GETList public organization events/orgs/{org}/events
• GETList public repositories/repositories
• GETList organizations/organizations
• GETGet a public SSH key for the authenticated user/user/keys/{key_id}
• GETList issue events/repos/{owner}/{repo}/issues/{issue_number}/events
• GETGet an issue comment/repos/{owner}/{repo}/issues/comments/{comment_id}
• GETList subscriptions for the authenticated user (stubbed)/user/marketplace_purchases/stubbed
• GETList issue comments/repos/{owner}/{repo}/issues/{issue_number}/comments
• GETList timeline events for an issue/repos/{owner}/{repo}/issues/{issue_number}/timeline
• GETCheck if a user is blocked by the authenticated user/user/blocks/{username}
• GETList gist comments/gists/{gist_id}/comments
• GETCheck if a person is followed by the authenticated user/user/following/{username}
• GETGet a GPG key for the authenticated user/user/gpg_keys/{gpg_key_id}
• GETGet contextual information for a user/users/{username}/hovercard
• GETGet a user installation for the authenticated app/users/{username}/installation

How automating GitHub works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live GitHub account.
4. Grant access, then go live. You approve the specific GitHub operations it may use — and only those.

Popular GitHub integrations

Connect GitHub to the tools people pair it with most.

• GitHub and OData for namespace microsoft.graphintegration
• GitHub and Cloudflareintegration
• GitHub and NetBoxintegration
• GitHub and Mistintegration
• GitHub and Loket.nlintegration
• GitHub and Atlassian The Jira Cloud platformintegration
• GitHub and Magento B2Bintegration
• GitHub and Stripeintegration
• GitHub and Zuora Reference Billingintegration
• GitHub and bunqintegration
• GitHub and DocuSignintegration
• GitHub and Zoomintegration

Automate GitHub with these

• Trello324 operations
• Bitbucket292 operations
• Orthanc Server Orthanc268 operations
• Asana249 operations
• Discord242 operations
• Slack174 operations
• Visualstudio VSOnline152 operations
• OnSched Setup138 operations
• StackExchange124 operations
• Slicebox118 operations
• Noosh application102 operations
• Attio90 operations

Categories

• Collaboration
• Developer tools

Questions about GitHub automation

Can HumDay connect to GitHub?

Yes. HumDay reads GitHub's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 811 operations are documented.

Do I need to write code to automate GitHub?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your GitHub account.

What can HumDay do in GitHub?

383 of the 811 documented operations change something in GitHub, and 428 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my GitHub account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to GitHub is held behind that approval.

Where this came from

The operations above are read from a published API description for GitHub at raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api. Descriptions are the provider’s own words, not ours. Last published 2023-02-15.