<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github on Samarthya</title><link>https://samarthya.me/tags/github/</link><description>Recent content in Github on Samarthya</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Samarthya 2018-2026. All rights reserved.</copyright><lastBuildDate>Tue, 27 Oct 2026 20:05:18 -0400</lastBuildDate><atom:link href="https://samarthya.me/tags/github/index.xml" rel="self" type="application/rss+xml"/><item><title>From finding to fix: Black Duck pull requests on GitHub Enterprise Server</title><link>https://samarthya.me/posts/ghes-blackduck-fix-prs/</link><pubDate>Tue, 27 Oct 2026 20:05:18 -0400</pubDate><guid>https://samarthya.me/posts/ghes-blackduck-fix-prs/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; A vulnerability report that nobody reads is a smoke alarm with no battery. The goal is not more findings. The&#10;goal is a pull request that a developer can review and merge before lunch.&#10;&lt;/div&gt;&#10;&#10;&#10;&lt;h2 class="relative group"&gt;Why this post&#10; &lt;div id="why-this-post" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-this-post" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;SentinelOne&amp;rsquo;s&#10;&lt;a href="https://www.sentinelone.com/cybersecurity-101/cybersecurity/github-vulnerability-management/" target="_blank" rel="noreferrer"&gt;overview of GitHub vulnerability management&lt;/a&gt;&#10;describes the job as &amp;ldquo;discovering, triaging, and remediating security vulnerabilities in GitHub repositories,&#10;dependencies, and workflows&amp;rdquo;. It lists the usual native tools: Dependabot, code scanning, secret scanning and&#10;security advisories. It also admits the gaps: no asset inventory or risk scoring, and dependencies that&#10;Dependabot cannot track.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://samarthya.me/posts/ghes-blackduck-fix-prs/feature.png"/></item><item><title>Moving to Hugo, part 3: Living with Hugo</title><link>https://samarthya.me/posts/moving-to-hugo-3-living-with-hugo/</link><pubDate>Mon, 26 Oct 2026 07:20:00 -0400</pubDate><guid>https://samarthya.me/posts/moving-to-hugo-3-living-with-hugo/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; Migrating is a project. Living with the result is a habit. Here&amp;rsquo;s what a normal week with a Hugo site looks&#10;like, and what to do when something needs updating.&#10;&lt;/div&gt;&#10;&#10;&#10;&lt;h2 class="relative group"&gt;Writing a post&#10; &lt;div id="writing-a-post" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#writing-a-post" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Every post is a folder. The theme&amp;rsquo;s archetype fills in the front matter for me:&lt;/p&gt;</description></item><item><title>Moving to Hugo, part 2: The migration playbook</title><link>https://samarthya.me/posts/moving-to-hugo-2-the-migration-playbook/</link><pubDate>Mon, 26 Oct 2026 07:10:00 -0400</pubDate><guid>https://samarthya.me/posts/moving-to-hugo-2-the-migration-playbook/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; Ten phases, in the order that kept my risk low. Each one ends with something you can check, so you always&#10;know whether it&amp;rsquo;s safe to move on.&#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;The numbers come from my own move: &lt;strong&gt;137 WordPress posts&lt;/strong&gt; from six years, a few hundred images, and a domain&#10;that also carried email. Your numbers will differ; the order shouldn&amp;rsquo;t.&lt;/p&gt;</description></item><item><title>The domain moved</title><link>https://samarthya.me/daily/2026/10/the-domain-moved/</link><pubDate>Sun, 25 Oct 2026 21:00:00 -0400</pubDate><guid>https://samarthya.me/daily/2026/10/the-domain-moved/</guid><description>&lt;p&gt;The scariest step, done. DNS moved to Cloudflare without changing a single record, mail checked in both&#10;directions, and only then was the website pointed at GitHub Pages.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;samarthya.me&lt;/strong&gt; serves the new site over HTTPS. &lt;code&gt;www&lt;/code&gt; redirects to it.&lt;/li&gt;&#10;&lt;li&gt;Every old &lt;code&gt;/wps/…&lt;/code&gt; link lands on the right post.&lt;/li&gt;&#10;&lt;li&gt;Wrote it all up: &lt;a href="https://samarthya.me/posts/rebuilding-1-the-day-the-blog-fell/" &gt;Rebuilding samarthya.me&lt;/a&gt;, in four parts.&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>Rebuilding samarthya.me, part 4: Moving the domain without losing mail</title><link>https://samarthya.me/posts/rebuilding-4-moving-the-domain/</link><pubDate>Sun, 25 Oct 2026 12:30:00 -0400</pubDate><guid>https://samarthya.me/posts/rebuilding-4-moving-the-domain/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; Moving a website is easy. Moving a website &lt;strong&gt;that shares a domain with your email&lt;/strong&gt; is where people lose mail&#10;for a weekend. This is how the switch went, in the order that kept everything working.&#10;&lt;/div&gt;&#10;&#10;&#10;&lt;h2 class="relative group"&gt;Three services, three jobs&#10; &lt;div id="three-services-three-jobs" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#three-services-three-jobs" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;It helps to separate what used to be bundled at one host:&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://samarthya.me/posts/rebuilding-4-moving-the-domain/feature.jpg"/></item><item><title>Rebuilding samarthya.me, part 3: A new home on Hugo</title><link>https://samarthya.me/posts/rebuilding-3-a-new-home-on-hugo/</link><pubDate>Sun, 25 Oct 2026 12:20:00 -0400</pubDate><guid>https://samarthya.me/posts/rebuilding-3-a-new-home-on-hugo/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; The content was safe. Now it needed a home that&amp;rsquo;s easy to keep alive: something I can write in, push, and&#10;forget about.&#10;&lt;/div&gt;&#10;&#10;&#10;&lt;h2 class="relative group"&gt;The stack&#10; &lt;div id="the-stack" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-stack" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://gohugo.io/" target="_blank" rel="noreferrer"&gt;Hugo&lt;/a&gt;&lt;/strong&gt;, pinned to one exact version with &lt;a href="https://mise.jdx.dev/" target="_blank" rel="noreferrer"&gt;mise&lt;/a&gt;, so a future&#10;release can&amp;rsquo;t silently break the build.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;&lt;a href="https://blowfish.page/" target="_blank" rel="noreferrer"&gt;Blowfish&lt;/a&gt;&lt;/strong&gt; as the theme, added as a git submodule and &lt;strong&gt;never edited&lt;/strong&gt;. Every&#10;change lives in the site&amp;rsquo;s own &lt;code&gt;layouts/&lt;/code&gt; and &lt;code&gt;assets/css/&lt;/code&gt;, so theme updates stay a one-line operation.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;GitHub Actions → GitHub Pages.&lt;/strong&gt; Push to &lt;code&gt;main&lt;/code&gt;, and about a minute later the site is rebuilt and live.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&#10;&lt;h2 class="relative group"&gt;A portal, not just a blog&#10; &lt;div id="a-portal-not-just-a-blog" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#a-portal-not-just-a-blog" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;The first version looked like what it was: an unmodified theme with 137 blank tiles. Imported posts have no&#10;&amp;ldquo;feature image&amp;rdquo;, so every card was empty. Three changes turned it into a place:&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://samarthya.me/posts/rebuilding-3-a-new-home-on-hugo/feature.jpg"/></item><item><title>Rebuilt on Hugo</title><link>https://samarthya.me/daily/2026/10/rebuilt-on-hugo/</link><pubDate>Sat, 24 Oct 2026 22:00:00 -0400</pubDate><guid>https://samarthya.me/daily/2026/10/rebuilt-on-hugo/</guid><description>&lt;p&gt;A long day, and a good one. The blog is now a static &lt;a href="https://gohugo.io/" target="_blank" rel="noreferrer"&gt;Hugo&lt;/a&gt; site: no database, no plugins,&#10;nothing to break into. It&amp;rsquo;s published straight from a git repository.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;137 posts&lt;/strong&gt; converted, and every old link redirects to its new address.&lt;/li&gt;&#10;&lt;li&gt;An old backup turned up &lt;strong&gt;126 of the missing images&lt;/strong&gt;. A handful are still gone for good.&lt;/li&gt;&#10;&lt;li&gt;A new homepage that says what this place is for, and topics that sort themselves.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Fall down, get up, build again.&lt;/p&gt;</description></item><item><title>Personal Access Token</title><link>https://samarthya.me/posts/personal-access-token/</link><pubDate>Thu, 23 Sep 2021 16:45:26 +0000</pubDate><guid>https://samarthya.me/posts/personal-access-token/</guid><description>&lt;p&gt;In case you are still using the basic/auth it is time to move to personal access token.&lt;/p&gt;&#10;&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; &lt;a href="https://docs.github.com/en/enterprise-server@3.1/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token" target="_blank" rel="noreferrer"&gt;Official documentation&lt;/a&gt; is the best guide.&#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;Personal access tokens (PATs) are an alternative to using &lt;code&gt;passwords&lt;/code&gt; for authentication to GitHub Enterprise Server when using the &lt;a href="https://docs.github.com/en/enterprise-server@3.1/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens" target="_blank" rel="noreferrer"&gt;GitHub API&lt;/a&gt; or the &lt;a href="https://docs.github.com/en/enterprise-server@3.1/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#using-a-token-on-the-command-line" target="_blank" rel="noreferrer"&gt;command line&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>