{"id":999,"date":"2026-05-20T04:50:38","date_gmt":"2026-05-20T04:50:38","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/?p=999"},"modified":"2026-05-20T04:50:38","modified_gmt":"2026-05-20T04:50:38","slug":"github-github-cli-gh-install-authenticate-and-use-github-from-the-terminal","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/github-github-cli-gh-install-authenticate-and-use-github-from-the-terminal\/","title":{"rendered":"Github: GitHub CLI gh \u2014 Install, Authenticate, and Use GitHub from the Terminal"},"content":{"rendered":"\n

1. What is gh<\/code>?<\/h2>\n\n\n\n

gh<\/code> is the official GitHub command-line interface<\/strong>. It brings GitHub features such as repositories, pull requests, issues, GitHub Actions, Codespaces, releases, secrets, variables, and API access into your terminal, right next to where you already use git<\/code>. GitHub describes it nicely: gh<\/code> lets you work with GitHub from the command line and avoid constantly switching between terminal and browser. (GitHub<\/a>)<\/p>\n\n\n\n

A simple way to remember it:<\/p>\n\n\n\n

git  # works with Git: commits, branches, remotes, merges\ngh   # works with GitHub: PRs, issues, Actions, releases, repos, APIs\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
git status\ngit add .\ngit commit -m \"Add login page\"\n\ngh pr create\n<\/code><\/pre>\n\n\n\n
So git<\/code> handles your source-control work, while gh<\/code> handles the GitHub workflow around it.<\/p>\n\n\n\n
\n\n\n\n
2. Install gh<\/code> on Windows, macOS, and Linux<\/h2>\n\n\n\n
Windows installation<\/h3>\n\n\n\n
The official recommended Windows method is WinGet<\/strong>. GitHub notes that the Windows installer modifies PATH, so after installing, open a new Windows Terminal window, not only a new tab. (GitHub<\/a>)<\/p>\n\n\n\n
winget install --id GitHub.cli --source winget\n<\/code><\/pre>\n\n\n\n
Upgrade:<\/p>\n\n\n\n
winget upgrade --id GitHub.cli --source winget\n<\/code><\/pre>\n\n\n\n
Community alternatives include Chocolatey, Scoop, Conda, and Webi, but the official recommendation is WinGet. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
macOS installation<\/h3>\n\n\n\n
The official recommended macOS method is Homebrew<\/strong>. (GitHub<\/a>)<\/p>\n\n\n\n
brew install gh\n<\/code><\/pre>\n\n\n\n
Upgrade:<\/p>\n\n\n\n
brew upgrade gh\n<\/code><\/pre>\n\n\n\n
GitHub also provides precompiled binaries for macOS amd64 and arm64, plus a universal installer. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
Linux installation<\/h3>\n\n\n\n
For Ubuntu, Debian, and Raspberry Pi OS, GitHub recommends the official Debian-style package repository. GitHub\u2019s Linux packages and repository metadata are signed, and the install docs list PGP key fingerprints for verification. (GitHub<\/a>)<\/p>\n\n\n\n
(type -p wget >\/dev\/null || (sudo apt update && sudo apt install wget -y)) \\\n  && sudo mkdir -p -m 755 \/etc\/apt\/keyrings \\\n  && out=$(mktemp) && wget -nv -O$out https:\/\/cli.github.com\/packages\/githubcli-archive-keyring.gpg \\\n  && cat $out | sudo tee \/etc\/apt\/keyrings\/githubcli-archive-keyring.gpg > \/dev\/null \\\n  && sudo chmod go+r \/etc\/apt\/keyrings\/githubcli-archive-keyring.gpg \\\n  && sudo mkdir -p -m 755 \/etc\/apt\/sources.list.d \\\n  && echo \"deb [arch=$(dpkg --print-architecture) signed-by=\/etc\/apt\/keyrings\/githubcli-archive-keyring.gpg] https:\/\/cli.github.com\/packages stable main\" \\\n    | sudo tee \/etc\/apt\/sources.list.d\/github-cli.list > \/dev\/null \\\n  && sudo apt update \\\n  && sudo apt install gh -y\n<\/code><\/pre>\n\n\n\n
Upgrade:<\/p>\n\n\n\n
sudo apt update\nsudo apt install gh\n<\/code><\/pre>\n\n\n\n
For Fedora\/RHEL\/CentOS-style systems using DNF5:<\/p>\n\n\n\n
sudo dnf install dnf5-plugins\nsudo dnf config-manager addrepo --from-repofile=https:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo\nsudo dnf install gh\n<\/code><\/pre>\n\n\n\n
For DNF4:<\/p>\n\n\n\n
sudo dnf install 'dnf-command(config-manager)'\nsudo dnf config-manager --add-repo https:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo\nsudo dnf install gh\n<\/code><\/pre>\n\n\n\n
For openSUSE\/SUSE:<\/p>\n\n\n\n
sudo zypper addrepo https:\/\/cli.github.com\/packages\/rpm\/gh-cli.repo\nsudo zypper ref\nsudo zypper install gh\n<\/code><\/pre>\n\n\n\n
GitHub\u2019s docs also mention Homebrew on Linux, precompiled binaries, and several community-maintained package options. They specifically discourage using Snap for GitHub CLI. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
3. Verify installation<\/h2>\n\n\n\n
After installing, check the version:<\/p>\n\n\n\n
gh --version\n<\/code><\/pre>\n\n\n\n
Then authenticate:<\/p>\n\n\n\n
gh auth login\n<\/code><\/pre>\n\n\n\n
The login flow asks whether you use GitHub.com or another GitHub Enterprise host, then walks you through browser-based authentication. If you choose HTTPS for Git operations, GitHub CLI can also store Git credentials so commands like git push<\/code> and git pull<\/code> work without separate credential setup. (GitHub Docs<\/a>)<\/p>\n\n\n\n
Check login status:<\/p>\n\n\n\n
gh auth status\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
4. Basic gh<\/code> command structure<\/h2>\n\n\n\n
Most commands follow this pattern:<\/p>\n\n\n\n
gh <area> <action> [options]\n<\/code><\/pre>\n\n\n\n
Examples:<\/p>\n\n\n\n
gh repo view\ngh repo clone owner\/repo\ngh issue list\ngh pr create\ngh workflow list\ngh run list\ngh release create\n<\/code><\/pre>\n\n\n\n
To see all top-level commands:<\/p>\n\n\n\n
gh\n<\/code><\/pre>\n\n\n\n
To see subcommands:<\/p>\n\n\n\n
gh repo\ngh pr\ngh issue\n<\/code><\/pre>\n\n\n\n
To get help:<\/p>\n\n\n\n
gh pr create --help\ngh repo clone --help\n<\/code><\/pre>\n\n\n\n
GitHub\u2019s reference says you can use gh<\/code> without arguments for top-level commands, gh COMMAND<\/code> for subcommands, and --help<\/code> for details on any command. (GitHub Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
5. Main capabilities of the gh<\/code> command line<\/h1>\n\n\n\n
GitHub CLI has a surprisingly wide command surface. The current manual includes core commands for auth, repositories, issues, pull requests, organizations, projects, releases, gists, Codespaces, and GitHub Actions, plus additional commands for API calls, aliases, completions, config, extensions, GPG keys, labels, rulesets, search, secrets, SSH keys, status, and variables. (GitHub CLI<\/a>)<\/p>\n\n\n\n
Repository management<\/h2>\n\n\n\n
gh repo clone owner\/repo\ngh repo view owner\/repo\ngh repo create\ngh repo fork owner\/repo\n<\/code><\/pre>\n\n\n\n
Real use case: You join a new project and need to clone the repo quickly.<\/p>\n\n\n\n
gh repo clone kubernetes\/kubernetes\ncd kubernetes\ngh repo view --web\n<\/code><\/pre>\n\n\n\n
Issue management<\/h2>\n\n\n\n
gh issue list\ngh issue view 42\ngh issue create\ngh issue close 42\n<\/code><\/pre>\n\n\n\n
Real use case: A tester finds a bug and creates an issue from the terminal.<\/p>\n\n\n\n
gh issue create \\\n  --title \"Login button disabled after password reset\" \\\n  --body \"Steps: reset password, log out, try to log in again. Expected: login button active. Actual: button remains disabled.\" \\\n  --label bug\n<\/code><\/pre>\n\n\n\n
Pull request workflow<\/h2>\n\n\n\n
gh pr list\ngh pr create\ngh pr checkout 123\ngh pr view 123\ngh pr review 123\ngh pr merge 123\n<\/code><\/pre>\n\n\n\n
Real use case: You finish a feature branch and create a PR without opening GitHub in the browser.<\/p>\n\n\n\n
git checkout -b feature\/add-profile-page\ngit add .\ngit commit -m \"Add profile page\"\ngit push -u origin feature\/add-profile-page\n\ngh pr create \\\n  --title \"Add profile page\" \\\n  --body \"Adds a user profile page with editable display name and avatar.\"\n<\/code><\/pre>\n\n\n\n
GitHub Actions<\/h2>\n\n\n\n
gh workflow list\ngh workflow run ci.yml\ngh run list\ngh run view\ngh run watch\ngh run download\n<\/code><\/pre>\n\n\n\n
Real use case: You push code and want to watch CI from the terminal.<\/p>\n\n\n\n
gh run list\ngh run watch\n<\/code><\/pre>\n\n\n\n
The gh run<\/code> command supports listing, viewing, watching, canceling, deleting, downloading logs\/artifacts, and rerunning workflow runs. (GitHub CLI<\/a>)<\/p>\n\n\n\n
Releases<\/h2>\n\n\n\n
gh release list\ngh release view v1.0.0\ngh release create v1.0.0\ngh release upload v1.0.0 .\/dist\/app.zip\n<\/code><\/pre>\n\n\n\n
Real use case: You build a CLI tool and publish a release with binaries.<\/p>\n\n\n\n
gh release create v1.0.0 .\/dist\/myapp-linux.tar.gz .\/dist\/myapp-macos.zip \\\n  --title \"v1.0.0\" \\\n  --notes \"First stable release.\"\n<\/code><\/pre>\n\n\n\n
Secrets and variables<\/h2>\n\n\n\n
gh secret set DOCKER_TOKEN\ngh secret list\ngh variable set APP_ENV --body production\ngh variable list\n<\/code><\/pre>\n\n\n\n
Real use case: You need to add a deployment token for GitHub Actions.<\/p>\n\n\n\n
gh secret set DOCKERHUB_TOKEN\n<\/code><\/pre>\n\n\n\n
Then paste the secret value when prompted.<\/p>\n\n\n\n
GitHub API access<\/h2>\n\n\n\n
gh api repos\/OWNER\/REPO\ngh api user\ngh api graphql\n<\/code><\/pre>\n\n\n\n
Real use case: You want to script a GitHub operation that does not have a dedicated high-level gh<\/code> command.<\/p>\n\n\n\n
gh api repos\/OWNER\/REPO\/issues\n<\/code><\/pre>\n\n\n\n
This is one of the sleeper superpowers of gh<\/code>: it gives you authenticated API access without manually managing tokens in every script.<\/p>\n\n\n\n
Codespaces<\/h2>\n\n\n\n
gh codespace list\ngh codespace create\ngh codespace ssh\ngh codespace code\n<\/code><\/pre>\n\n\n\n
Real use case: You are on a lightweight laptop and want to develop inside a cloud dev environment.<\/p>\n\n\n\n
gh codespace create\ngh codespace code\n<\/code><\/pre>\n\n\n\n
GitHub\u2019s quickstart shows gh codespace create<\/code>, gh codespace list<\/code>, and gh codespace code -w<\/code> as common Codespaces commands. (GitHub Docs<\/a>)<\/p>\n\n\n\n
Search<\/h2>\n\n\n\n
gh search repos \"language:go stars:>1000\"\ngh search issues \"is:open label:bug\"\ngh search prs \"review-requested:@me state:open\"\n<\/code><\/pre>\n\n\n\n
Real use case: You want to find all open PRs awaiting your review.<\/p>\n\n\n\n
gh search prs --review-requested=@me --state=open\n<\/code><\/pre>\n\n\n\n
GitHub\u2019s quickstart uses this exact pattern for PR review discovery. (GitHub Docs<\/a>)<\/p>\n\n\n\n
Aliases and customization<\/h2>\n\n\n\n
gh alias set co \"pr checkout\"\ngh alias set prd \"pr create --draft\"\n<\/code><\/pre>\n\n\n\n
Then use:<\/p>\n\n\n\n
gh co 123\ngh prd\n<\/code><\/pre>\n\n\n\n
GitHub\u2019s docs mention aliases and extensions as ways to customize the CLI for your workflow. (GitHub Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
6. End-to-end real-world workflows<\/h1>\n\n\n\n
Workflow 1: New developer joining a project<\/h2>\n\n\n\n
Scenario: You are assigned to a repository and need to clone it, inspect it, and check assigned work.<\/p>\n\n\n\n
gh auth login\ngh repo clone my-org\/my-app\ncd my-app\ngh repo view\ngh issue list --assignee \"@me\"\ngh pr list\n<\/code><\/pre>\n\n\n\n
Why this is useful: onboarding becomes faster. You can see the README, issues, and PRs without bouncing between browser tabs.<\/p>\n\n\n\n
\n\n\n\n
Workflow 2: Create a bug report from terminal<\/h2>\n\n\n\n
Scenario: You are testing an app and discover a bug.<\/p>\n\n\n\n
gh issue create \\\n  --title \"Checkout fails when coupon code is empty\" \\\n  --body \"Steps to reproduce:\n1. Open checkout page\n2. Leave coupon code empty\n3. Click Apply\n\nExpected: no error\nActual: checkout form crashes\" \\\n  --label bug\n<\/code><\/pre>\n\n\n\n
Then list bugs:<\/p>\n\n\n\n
gh issue list --label bug\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Workflow 3: Create a pull request<\/h2>\n\n\n\n
Scenario: You fixed an issue and want to open a PR.<\/p>\n\n\n\n
git checkout -b fix\/checkout-empty-coupon\ngit add .\ngit commit -m \"Fix checkout crash for empty coupon\"\ngit push -u origin fix\/checkout-empty-coupon\n\ngh pr create \\\n  --title \"Fix checkout crash for empty coupon\" \\\n  --body \"Fixes validation when coupon field is empty.\"\n<\/code><\/pre>\n\n\n\n
Open the PR in browser only when needed:<\/p>\n\n\n\n
gh pr view --web\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Workflow 4: Review someone else\u2019s PR locally<\/h2>\n\n\n\n
Scenario: A teammate asks you to review PR #58.<\/p>\n\n\n\n
gh pr checkout 58\nnpm test\ngh pr view\ngh pr review 58 --comment --body \"Tested locally. Left one small suggestion.\"\n<\/code><\/pre>\n\n\n\n
Approve:<\/p>\n\n\n\n
gh pr review 58 --approve\n<\/code><\/pre>\n\n\n\n
Merge:<\/p>\n\n\n\n
gh pr merge 58 --squash --delete-branch\n<\/code><\/pre>\n\n\n\n
Tiny quality-of-life upgrade, huge time saver.<\/p>\n\n\n\n
\n\n\n\n
Workflow 5: Watch CI\/CD after pushing code<\/h2>\n\n\n\n
Scenario: You pushed a branch and want to see whether GitHub Actions passed.<\/p>\n\n\n\n
gh run list\ngh run watch\n<\/code><\/pre>\n\n\n\n
View logs for a failed run:<\/p>\n\n\n\n
gh run view --log\n<\/code><\/pre>\n\n\n\n
Rerun failed jobs:<\/p>\n\n\n\n
gh run rerun --failed\n<\/code><\/pre>\n\n\n\n
This is especially useful in DevOps, platform engineering, and CI\/CD-heavy teams.<\/p>\n\n\n\n
\n\n\n\n
Workflow 6: Trigger a deployment workflow manually<\/h2>\n\n\n\n
Scenario: Your repo has a deployment workflow that supports manual runs.<\/p>\n\n\n\n
gh workflow list\ngh workflow run deploy.yml\ngh run watch\n<\/code><\/pre>\n\n\n\n
With inputs:<\/p>\n\n\n\n
gh workflow run deploy.yml \\\n  -f environment=staging \\\n  -f version=v1.2.3\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Workflow 7: Publish a release<\/h2>\n\n\n\n
Scenario: You built version v1.0.0<\/code> of your app.<\/p>\n\n\n\n
git tag v1.0.0\ngit push origin v1.0.0\n\ngh release create v1.0.0 \\\n  .\/dist\/app-linux-amd64.tar.gz \\\n  .\/dist\/app-darwin-arm64.zip \\\n  --title \"v1.0.0\" \\\n  --notes \"Initial production release.\"\n<\/code><\/pre>\n\n\n\n
View releases:<\/p>\n\n\n\n
gh release list\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Workflow 8: Use gh<\/code> inside automation scripts<\/h2>\n\n\n\n
Scenario: You want to script GitHub tasks.<\/p>\n\n\n\n
#!\/usr\/bin\/env bash\nset -e\n\nREPO=\"my-org\/my-app\"\n\necho \"Open issues:\"\ngh issue list --repo \"$REPO\" --state open\n\necho \"Open PRs:\"\ngh pr list --repo \"$REPO\" --state open\n<\/code><\/pre>\n\n\n\n
For structured output, many gh<\/code> commands support JSON output:<\/p>\n\n\n\n
gh pr list --json number,title,author,state\n<\/code><\/pre>\n\n\n\n
That makes gh<\/code> handy for shell scripts, dashboards, reports, and automation.<\/p>\n\n\n\n
\n\n\n\n
7. Handy commands cheat sheet<\/h1>\n\n\n\n
Task<\/th>Command<\/th><\/tr><\/thead>
Login<\/td>gh auth login<\/code><\/td><\/tr>
Check login<\/td>gh auth status<\/code><\/td><\/tr>
Clone repo<\/td>gh repo clone owner\/repo<\/code><\/td><\/tr>
View repo<\/td>gh repo view<\/code><\/td><\/tr>
Create repo<\/td>gh repo create<\/code><\/td><\/tr>
List issues<\/td>gh issue list<\/code><\/td><\/tr>
Create issue<\/td>gh issue create<\/code><\/td><\/tr>
List PRs<\/td>gh pr list<\/code><\/td><\/tr>
Create PR<\/td>gh pr create<\/code><\/td><\/tr>
Checkout PR<\/td>gh pr checkout 123<\/code><\/td><\/tr>
Review PR<\/td>gh pr review 123<\/code><\/td><\/tr>
Merge PR<\/td>gh pr merge 123<\/code><\/td><\/tr>
List workflows<\/td>gh workflow list<\/code><\/td><\/tr>
Run workflow<\/td>gh workflow run workflow.yml<\/code><\/td><\/tr>
List workflow runs<\/td>gh run list<\/code><\/td><\/tr>
Watch workflow run<\/td>gh run watch<\/code><\/td><\/tr>
Create release<\/td>gh release create v1.0.0<\/code><\/td><\/tr>
Set secret<\/td>gh secret set NAME<\/code><\/td><\/tr>
Set variable<\/td>gh variable set NAME --body value<\/code><\/td><\/tr>
Open repo\/PR\/page in browser<\/td>gh browse<\/code><\/td><\/tr>
Call GitHub API<\/td>gh api ...<\/code><\/td><\/tr>
Create alias<\/td>gh alias set name \"command\"<\/code><\/td><\/tr>
Install extension<\/td>gh extension install owner\/gh-extension<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\n
8. Recommended beginner practice lab<\/h1>\n\n\n\n
Try this safe practice workflow on a test repository.<\/p>\n\n\n\n
gh auth login\ngh repo create gh-practice-demo --public --clone\ncd gh-practice-demo\n\necho \"# GH Practice Demo\" > README.md\ngit add README.md\ngit commit -m \"Add README\"\ngit push origin main\n<\/code><\/pre>\n\n\n\n
Create an issue:<\/p>\n\n\n\n
gh issue create \\\n  --title \"Add installation instructions\" \\\n  --body \"The README should include setup steps.\"\n<\/code><\/pre>\n\n\n\n
Create a branch and PR:<\/p>\n\n\n\n
git checkout -b docs\/install-steps\necho \"\" >> README.md\necho \"## Installation\" >> README.md\necho \"Run the app setup commands here.\" >> README.md\n\ngit add README.md\ngit commit -m \"Add installation section\"\ngit push -u origin docs\/install-steps\n\ngh pr create \\\n  --title \"Add installation section\" \\\n  --body \"Adds basic installation instructions to README.\"\n<\/code><\/pre>\n\n\n\n
Merge it:<\/p>\n\n\n\n
gh pr merge --squash --delete-branch\n<\/code><\/pre>\n\n\n\n
Clean up:<\/p>\n\n\n\n
git checkout main\ngit pull\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
9. Best practices<\/h1>\n\n\n\n
Use gh auth status<\/code> when commands fail mysteriously. A lot of \u201cwhy is GitHub rejecting me?\u201d problems are just expired or missing auth.<\/p>\n\n\n\n
Use --help<\/code> aggressively:<\/p>\n\n\n\n
gh pr create --help\ngh workflow run --help\ngh release create --help\n<\/code><\/pre>\n\n\n\n
Use aliases for commands you repeat often:<\/p>\n\n\n\n
gh alias set mine \"issue list --assignee @me\"\ngh alias set reviews \"search prs --review-requested=@me --state=open\"\n<\/code><\/pre>\n\n\n\n
Use gh pr checkout<\/code> instead of manually finding branches from forks. It is cleaner and less error-prone.<\/p>\n\n\n\n
Use gh run watch<\/code> right after pushing a PR. It keeps your feedback loop tight.<\/p>\n\n\n\n
For Linux, prefer GitHub\u2019s official package repositories over stale distro packages when available. GitHub\u2019s own Linux install docs warn that some community Debian\/Ubuntu packages had broken older versions due to deprecated GitHub APIs as of November 2025. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
10. Final summary<\/h1>\n\n\n\n
gh<\/code> is one of those tools that feels small at first, then quietly takes over your workflow. For developers, it speeds up cloning repos, creating issues, opening PRs, reviewing code, and checking CI. For DevOps teams, it helps trigger workflows, inspect GitHub Actions, manage secrets, publish releases, and script GitHub operations. For open-source maintainers, it makes triage and PR review dramatically faster.<\/p>\n\n\n\n
Start with these five commands:<\/p>\n\n\n\n
gh auth login\ngh repo clone owner\/repo\ngh issue list\ngh pr create\ngh run watch\n<\/code><\/pre>\n\n\n\n
Once those feel natural, add releases, secrets, API calls, aliases, and workflow automation. That is where gh<\/code> turns from \u201cnice CLI tool\u201d into a proper GitHub power tool.<\/p>\n","protected":false},"excerpt":{"rendered":"
1. What is gh? gh is the official GitHub command-line interface. It brings GitHub features such as repositories, pull requests, issues, GitHub Actions, Codespaces, releases, secrets, variables,… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-999","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/999","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=999"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/999\/revisions"}],"predecessor-version":[{"id":1000,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/999\/revisions\/1000"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}