<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tokens on ayyzenn</title><link>https://ayyzenn.github.io/tags/tokens/</link><description>Recent content in Tokens on ayyzenn</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><lastBuildDate>Sat, 04 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://ayyzenn.github.io/tags/tokens/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub CLI and Personal Access Tokens: What I Use Daily</title><link>https://ayyzenn.github.io/posts/git_tools/</link><pubDate>Sat, 04 Sep 2021 00:00:00 +0000</pubDate><guid>https://ayyzenn.github.io/posts/git_tools/</guid><description>&lt;h2 id="why-i-bother-with-this"&gt;Why I Bother With This&lt;/h2&gt;
&lt;p&gt;I got tired of opening the browser every time I wanted to create a repo, check a PR, or trigger a workflow. &lt;strong&gt;GitHub CLI&lt;/strong&gt; (&lt;code&gt;gh&lt;/code&gt;) lets me do most of that from the terminal. &lt;strong&gt;Personal Access Tokens (PATs)&lt;/strong&gt; are how Git authenticates when you push over HTTPS.&lt;/p&gt;
&lt;p&gt;This post covers both — how I generate a PAT and how I use &lt;code&gt;gh&lt;/code&gt; day to day.&lt;/p&gt;</description></item></channel></rss>