{"id":1437,"date":"2019-10-27T21:24:48","date_gmt":"2019-10-27T21:24:48","guid":{"rendered":"https:\/\/www.ciraltos.com\/?p=1437"},"modified":"2023-03-23T22:43:22","modified_gmt":"2023-03-24T03:43:22","slug":"git-and-vs-code-for-the-lone-scripter","status":"publish","type":"post","link":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/","title":{"rendered":"Git and VS Code for the Lone Scripter"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

This is where my last two articles, Git for System Admin Scripting<\/a> and Get Started with Git Remote<\/a>, come together.  Microsoft\u2019s Visual Studio Code (VS Code) is a powerful and extendable IDE.  VS Code supports Git out of the box.  It also supports many programming and scripting languages with Microsoft and 3rd<\/sup> party extensions.  In this article, I walk through common tasks that we have already covered, only this time with the native Git integration within VS Code.  I also review new functionality with a free 3rd party extension. <\/p>\n\n\n\n\n\n\n\n

If you haven\u2019t used VS Code already, it can be downloaded and installed from here<\/a>.  I recommend the User installer<\/em> if using Windows.  I suspect there are other wonderful IDE\u2019s with Git integration available. If you have another product with similar functionality you prefer, please let me know.  Leave a message in the comments below of what it is and why you like it.<\/p>\n\n\n\n

This article assumes the reader has basic knowledge of Git covered\nin my previous two articles.  In addition,\nyou will need VS Code and Git Bash installed along with a GitHub account.  Let\u2019s jump right into using Git and VS Code.<\/p>\n\n\n\n

Git Clone<\/h2>\n\n\n\n

I rarely initiate a repository on a local machine.  I typically start a new project from the remote repository, GitHub in this case.  This way I can create the README.md, and .gitignore files as well as set it as private or public.  Once you have the repository setup, go to the green button labeled Clone or Download<\/em>.  Copy the web URL for the repository, this is needed shortly. <\/p>\n\n\n\n

Now go to VS Code.  I\u2019m\ngoing to clone a private repository to my local machine.  Start at the command pallet in VS Code by\npressing Ctrl+Shift+P (Command+Shift+P on Mac) and type the command: Git: Clone<\/em> and press enter.  As you can imagine, this starts the Git Clone\nprocess.<\/p>\n\n\n\n

\"\"<\/a>
Command Git Clone <\/figcaption><\/figure>\n\n\n\n

The next step asks for the Repository URL that was copied to\nthe clipboard a couple of paragraphs ago. \nPaste it into the Command Pallet and hit enter to continue.  You may get a login prompt for the GitHub\naccount if you haven\u2019t already logged in. \n<\/p>\n\n\n\n

\"\"<\/a>
Command Git Clone URL <\/figcaption><\/figure>\n\n\n\n

Next, VS Code will prompt for a location.  This is the most confusing part of the\nprocess.  VS Code is not prompting for\nthe location of the repository files, it\u2019s prompting for a location to create a\nfolder for the repository.  For example,\nI select my GitHub folder, and VS Code creates a new folder in that directory\nwith the name of the repository. \nConfiguration and code files are located in that folder.<\/p>\n\n\n\n

\"\"<\/a>
Select Repository Location <\/figcaption><\/figure>\n\n\n\n

Once added, you are asked to open the workspace or add it to\nthe existing workspace.  Either is fine,\nI prefer to open the workspace.<\/p>\n\n\n\n

\"\"<\/a>
Open Repository <\/figcaption><\/figure>\n\n\n\n

That\u2019s all it takes to clone the repository.  VS Code displays the files in the folder\nunder Explorer.  Open one of the files,\nmake a change and save it.  You may\nnotice that the file icon on the top left has a \u201c1\u201d in a blue circle next to\nit.  That indicates one file has been\nchanged and not saved.  Save the file and\nthe blue \u201c1\u201d will go away.<\/p>\n\n\n\n

\"\"<\/a>
Unsaved File <\/figcaption><\/figure>\n\n\n\n

Git Commit<\/h2>\n\n\n\n

If you are following along, you may have noticed that the blue \u201c1\u201d moved from the file icon to an icon with three dots connected by two lines.  That is the icon for source control and indicates that there is a change that has not been committed yet.  This is a convenient reminder of file commit status.  When ready to commit, go to the Source Control section and stage the files.  This is done by hovering over the file name and clicking the + sign as shown below.<\/p>\n\n\n\n

\"\"<\/a>
Stage Changes <\/figcaption><\/figure>\n\n\n\n

Alternatively, if there are multiple files, hover over Changes<\/em>\nand click the + sign to add all.  These\ntwo steps are the same as running the git add <\/em>or git add<\/em> –A<\/em>\ncommand.<\/p>\n\n\n\n

\"\"<\/a>
Save All Changes <\/figcaption><\/figure>\n\n\n\n

Next is the Commit. \nVS Code provides a location to enter a message.  Once a message is entered, click the checkmark\nto commit the changes. This does the same as the git commit<\/em> command.<\/p>\n\n\n\n

\"\"<\/a>
Git Commit <\/figcaption><\/figure>\n\n\n\n

Git Push and Git Pull<\/h2>\n\n\n\n

So far, changes have been made to a file, and the file has\nbeen staged and committed with VS Code.  However,\nthe online repository does not reflect any of those changes yet.  For that, we need to push the changes to the\nremote repository.  To push the changes, click\non the three dots in Source Control.  A drop-down\nlist displays with multiple options. \nClick on Push<\/em> to push the file to the remote repository.<\/p>\n\n\n\n

\"\"<\/a>
Git Push and Pull <\/figcaption><\/figure>\n\n\n\n

The last commit is now visible in the remote GitHub\nrepository under commit history.<\/p>\n\n\n\n

\"\"<\/a>
Commit from VS Code <\/figcaption><\/figure>\n\n\n\n

Notice the drop-down also had the Pull<\/em> option.  This works the same as the git pull<\/em>\ncommand, copying remote changes down to the local copy of the repository.  The process to initiate a Pull and a Push is\nthe same in VS Code.<\/p>\n\n\n\n

Git Lens<\/h2>\n\n\n\n

Next, functionality is added to VS Code with an extension called\nGit Lens.  To install, go to the Extensions\npanel in VS Code.  The Extensions icon\nhas 4 squares that make up another square (see below).  Search for Git Lens and click the green Install\n<\/em>button to get Git Lens.<\/p>\n\n\n\n

\"\"<\/a>
Install Git Lens <\/figcaption><\/figure>\n\n\n\n

View Change Log<\/h3>\n\n\n\n

Once Git Lens is installed, go back to a file in the repository\nand click on a line.  Notice in very\nlight text there is a message indicating who made the last change, when it was\nchanged, and the commit message.  This is\ndata Git Lens pulls from the. git folder about the last commit.  <\/p>\n\n\n\n

\"\"<\/a>
Change Log <\/figcaption><\/figure>\n\n\n\n

View Past Versions<\/h3>\n\n\n\n

I demonstrated how to view the contents of a file from a previous commit in my first article in this series.  That was good, but it would be difficult to identify changes in large files.  Below I use Git Lens to do a side-by-side comparison of a file and a previous commit.<\/p>\n\n\n\n

Make sure a file with committed changes is open and selected\nin the VS Code editor.  Go to the Git\nLens Icon (see below).  Under File\nhistory, click on one of the commits to the file.  VS Code opens the previously committed file\nand compares it with the current version. \nContent added is highlighted in green and deleted lines are indicated in\nred.  This is incredibly helpful for identifying\nchanges in versions of a script.<\/p>\n\n\n\n

\"\"<\/a>
View Past Versions <\/figcaption><\/figure>\n\n\n\n

Summary<\/h2>\n\n\n\n

I have used VS Code and GitHub as a source code repository for PowerShell Scripts, ARM templates and Terraform files for over two years.  While a file share, USB drive or cloud storage may be okay for storing scripts, I hope you understand why Git is the best option available for code management, even for System Admins and lone scripters.  <\/p>\n\n\n\n

This series was intentionally limited to features of VS Code and Git that I use and believe other System Admins and Lone Scripters may find helpful.  If you have any additional information, tools or processes that may help lone scripters with VS Code and Git, please let everyone know in the comments below.<\/p>\n","protected":false},"excerpt":{"rendered":"

This is where my last two articles, Git for System Admin Scripting and Get Started with Git Remote, come together.  Microsoft\u2019s Visual Studio Code (VS Code) is a powerful and extendable IDE.  VS Code supports Git out of the box.  It also supports many programming and scripting languages with Microsoft and 3rd party extensions.  In …<\/p>\n

Git and VS Code for the Lone Scripter<\/span> Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":3976,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":""},"categories":[170,8],"tags":[582,583,230,210,579,341,338,20,340,68],"yoast_head":"\nGit and VS Code for the Lone Scripter - ciraltos<\/title>\n<meta name=\"description\" content=\"In this article, I walk through common Git code management tasks with the native Git integration within VS Code. I also cover using Git Lens to view change logs and previous file versions.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Git and VS Code for the Lone Scripter - ciraltos\" \/>\n<meta property=\"og:description\" content=\"In this article, I walk through common Git code management tasks with the native Git integration within VS Code. I also cover using Git Lens to view change logs and previous file versions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\" \/>\n<meta property=\"og:site_name\" content=\"ciraltos\" \/>\n<meta property=\"article:published_time\" content=\"2019-10-27T21:24:48+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-03-24T03:43:22+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/VSGit.png\" \/>\n\t<meta property=\"og:image:width\" content=\"400\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Travis Roberts\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@ciraltos\" \/>\n<meta name=\"twitter:site\" content=\"@ciraltos\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Travis Roberts\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\"},\"author\":{\"name\":\"Travis Roberts\",\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\"},\"headline\":\"Git and VS Code for the Lone Scripter\",\"datePublished\":\"2019-10-27T21:24:48+00:00\",\"dateModified\":\"2023-03-24T03:43:22+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\"},\"wordCount\":1286,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\"},\"keywords\":[\".bat file\",\".ps1 file\",\"Automation\",\"Azure Automation\",\"Bash\",\"git\",\"github\",\"Powershell\",\"runbooks\",\"script\"],\"articleSection\":[\"PowerShell\",\"Trends\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\",\"url\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\",\"name\":\"Git and VS Code for the Lone Scripter - ciraltos\",\"isPartOf\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#website\"},\"datePublished\":\"2019-10-27T21:24:48+00:00\",\"dateModified\":\"2023-03-24T03:43:22+00:00\",\"description\":\"In this article, I walk through common Git code management tasks with the native Git integration within VS Code. I also cover using Git Lens to view change logs and previous file versions.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\/\/www.ciraltos.com\/staging2\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Git and VS Code for the Lone Scripter\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#website\",\"url\":\"http:\/\/www.ciraltos.com\/staging2\/\",\"name\":\"ciraltos\",\"description\":\"cloud, technology and trends\",\"publisher\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/www.ciraltos.com\/staging2\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a\",\"name\":\"Travis Roberts\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png\",\"contentUrl\":\"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png\",\"width\":5657,\"height\":3563,\"caption\":\"Travis Roberts\"},\"logo\":{\"@id\":\"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/\"},\"sameAs\":[\"http:\/\/www.ciraltos.com\",\"https:\/\/twitter.com\/ciraltos\"],\"url\":\"https:\/\/www.ciraltos.com\/staging2\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Git and VS Code for the Lone Scripter - ciraltos","description":"In this article, I walk through common Git code management tasks with the native Git integration within VS Code. I also cover using Git Lens to view change logs and previous file versions.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/","og_locale":"en_US","og_type":"article","og_title":"Git and VS Code for the Lone Scripter - ciraltos","og_description":"In this article, I walk through common Git code management tasks with the native Git integration within VS Code. I also cover using Git Lens to view change logs and previous file versions.","og_url":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/","og_site_name":"ciraltos","article_published_time":"2019-10-27T21:24:48+00:00","article_modified_time":"2023-03-24T03:43:22+00:00","og_image":[{"width":400,"height":400,"url":"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/VSGit.png","type":"image\/png"}],"author":"Travis Roberts","twitter_card":"summary_large_image","twitter_creator":"@ciraltos","twitter_site":"@ciraltos","twitter_misc":{"Written by":"Travis Roberts","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#article","isPartOf":{"@id":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/"},"author":{"name":"Travis Roberts","@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a"},"headline":"Git and VS Code for the Lone Scripter","datePublished":"2019-10-27T21:24:48+00:00","dateModified":"2023-03-24T03:43:22+00:00","mainEntityOfPage":{"@id":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/"},"wordCount":1286,"commentCount":0,"publisher":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a"},"keywords":[".bat file",".ps1 file","Automation","Azure Automation","Bash","git","github","Powershell","runbooks","script"],"articleSection":["PowerShell","Trends"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/","url":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/","name":"Git and VS Code for the Lone Scripter - ciraltos","isPartOf":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#website"},"datePublished":"2019-10-27T21:24:48+00:00","dateModified":"2023-03-24T03:43:22+00:00","description":"In this article, I walk through common Git code management tasks with the native Git integration within VS Code. I also cover using Git Lens to view change logs and previous file versions.","breadcrumb":{"@id":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.ciraltos.com\/staging2\/git-and-vs-code-for-the-lone-scripter\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/www.ciraltos.com\/staging2\/"},{"@type":"ListItem","position":2,"name":"Git and VS Code for the Lone Scripter"}]},{"@type":"WebSite","@id":"http:\/\/www.ciraltos.com\/staging2\/#website","url":"http:\/\/www.ciraltos.com\/staging2\/","name":"ciraltos","description":"cloud, technology and trends","publisher":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/www.ciraltos.com\/staging2\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/25391996d6cddfecd4d257162b7e373a","name":"Travis Roberts","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/","url":"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png","contentUrl":"https:\/\/www.ciraltos.com\/staging2\/wp-content\/uploads\/2023\/03\/Logo-1.png","width":5657,"height":3563,"caption":"Travis Roberts"},"logo":{"@id":"http:\/\/www.ciraltos.com\/staging2\/#\/schema\/person\/image\/"},"sameAs":["http:\/\/www.ciraltos.com","https:\/\/twitter.com\/ciraltos"],"url":"https:\/\/www.ciraltos.com\/staging2\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts\/1437"}],"collection":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/comments?post=1437"}],"version-history":[{"count":6,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts\/1437\/revisions"}],"predecessor-version":[{"id":3986,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/posts\/1437\/revisions\/3986"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/media\/3976"}],"wp:attachment":[{"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/media?parent=1437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/categories?post=1437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ciraltos.com\/staging2\/wp-json\/wp\/v2\/tags?post=1437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}