Webhooks

Webhooks Receive a web request with a JSON payload This trigger fires every time the Maker service receives a web request to notify it of an event. For information on triggering events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile) Developer info API endpoint slug maker_webhooks.json_event Trigger fields Event Text input > Other Label Event Name Helper text The name of the event, like "button_pressed" or "front_door_opened". Use only letters, numbers, and underscores Slug event Required true Can have default value true Ingredients Event name The name of the event that was triggered. Slug event_name Filter code MakerWebhooks.jsonEvent.EventName Type String Example buzzer Json payload JSON payload sent with the event. Slug json_body Filter code MakerWebhooks.jsonEvent.JsonPayload Type String Example {"data": "Hello, world!"} Occurred at Date and time event occurred. Slug occurred_at Filter code MakerWebhooks.jsonEvent.OccurredAt Type Date with time (ISO8601) Example 2020-07-08T04:17:06+05:00

gh auth login gh auth login [flags] Authenticate with a GitHub host. The default hostname is github.com. This can be overridden using the --hostname flag. The default authentication mode is a web-based browser flow. After completion, an authentication token will be stored securely in the system credential store. If a credential store is not found or there is an issue using it gh will fallback to writing the token to a plain text file. See gh auth status for its stored location. Alternatively, use --with-token to pass in a personal access token (classic) on standard input. The minimum required scopes for the token are: repo, read:org, and gist. Take care when passing a fine-grained personal access token to --with-token as the inherent scoping to certain resources may cause confusing behaviour when interacting with other resources. Favour setting GH_TOKEN$ for fine-grained personal access token usage. Alternatively, gh will use the authentication token found in environment variables. This method is most suitable for "headless" use of gh such as in automation. See gh help environment for more info. To use gh in GitHub Actions, add GH_TOKEN: ${{ github.token }} to env. The git protocol to use for git operations on this host can be set with --git-protocol, or during the interactive prompting. Although login is for a single account on a host, setting the git protocol will take effect for all users on the host. Specifying ssh for the git protocol will detect existing SSH keys to upload, prompting to create and upload a new key if one is not found. This can be skipped with --skip-ssh-key flag. For more information on OAuth scopes, https://docs.github.com/en/developers/apps/building-oauth-apps/scopes-for-oauth-apps/. Options -p, --git-protocol <string> The protocol to use for git operations on this host: {ssh|https} -h, --hostname <string> The hostname of the GitHub instance to authenticate with --insecure-storage Save authentication credentials in plain text instead of credential store -s, --scopes <strings> Additional authentication scopes to request --skip-ssh-key Skip generate/upload SSH key prompt -w, --web Open a browser to authenticate --with-token Read token from standard input Examples # Start interactive setup $ gh auth login # Authenticate against github.com by reading the token from a file $ gh auth login --with-token < mytoken.txt # Authenticate with specific host $ gh auth login --hostname enterprise.internal See also gh auth

brew install gh or

About creating GitHub Apps GitHub Apps let you build integrations to automate processes and extend GitHub's functionality. In this article About GitHub Apps Building a GitHub App Understanding what type of GitHub App to build About GitHub Apps A GitHub App is a type of integration that you can build to interact with and extend the functionality of GitHub. You can build a GitHub App to provide flexibility and reduce friction in your processes, without needing to sign in a user or create a service account. Common use cases for GitHub Apps include: Automating tasks or background processes Supporting "Sign in with GitHub," which allows users to sign in with their GitHub account to provide their identity in your ecosystem As a developer tool, allowing users to work with GitHub by signing into your GitHub App, which can then act on their behalf Integrating your tool or external service with GitHub Like OAuth apps, GitHub Apps use OAuth 2.0 and can act on behalf of a user. Unlike OAuth apps, GitHub Apps can also act independently of a user. GitHub Apps can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. By default, only organization owners can manage the settings of GitHub Apps in an organization. To allow additional users to change the developer settings of GitHub Apps owned by the organization, an owner can grant them GitHub App manager permissions. GitHub App Managers can't manage third-party applications. For more information about adding and removing GitHub App managers in your organization, see Roles in an organization.

Codespaces

Codespaces documentation Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to. OverviewQuickstart