Synchronized build

lektor-bot · lektor-bot · commit 55952a903974 · 2020-08-26T21:25:36.000Z
diff --git a/blog/entries/automate-github-for-more-than-CI CD/index.html b/blog/entries/automate-github-for-more-than-CI CD/index.html
@@ -280,7 +280,7 @@ <h2 class="title">Automate GitHub for more than CI/CD</h2>
 </blockquote>
 <p>In late 2018, in the midst of being acquired by Microsoft, GitHub <a href="https://github.blog/2018-10-16-future-of-software/">launched Github Actions</a> into public beta, allowing users to run code on the popular development platform for the first time. With a straightforward <code>YAML</code> configuration syntax and the power of Microsoft's Azure cloud, GitHub Actions quickly rose to compete with existing Continuous Integration (CI) and Continuous Deployment (CD) platforms like <strong>Circle CI</strong> and <strong>Travis CI</strong>. GitHub Actions made it easier than ever for developers to test and deploy software in the cloud, but from the beginning GitHub had bigger plans for the service.</p>
 <p>In a <a href="https://techcrunch.com/2018/10/16/github-launches-actions-its-workflow-automation-tool/">2018 TechCrunch interview</a>, GitHub's then head of platform acknowledged the usefulness of actions for more than CI/CD. "I see CI/CD as one narrow use case of actions. It’s so, so much more,” Lambert stressed. “And I think it’s going to revolutionize DevOps because people are now going to build best in breed deployment workflows for specific applications and frameworks, and those become the de facto standard shared on GitHub. […] It’s going to do everything we did for open source again for the DevOps space and for all those different parts of that workflow ecosystem."</p>
-<p>At Creative Commons, we use Github Actions and Bots on many of <a href="https://github.com/creativecommons?type=source">our open-source projects</a> for more than CI/CD—to manage our <a href="http://localhost:5000/community/community-team/">community team</a>; to automate repository health; and to automate tedious but frequent tasks. The following examples are just a small snapshot of our existing and in-progress automations.</p>
+<p>At Creative Commons, we use Github Actions and Bots on many of <a href="https://github.com/creativecommons?type=source">our open-source projects</a> for more than CI/CD—to manage our <a href="/community/community-team/">community team</a>; to automate repository health; and to automate tedious but frequent tasks. The following examples are just a small snapshot of our existing and in-progress automations.</p>
 <h2 id="example-automations">Example automations</h2><p><!-- no toc --></p>
 <ul>
 <li><a href="/blog/entries/automate-github-for-more-than-CI CD/#automatic-release-note-generation">Release note generation</a></li>
diff --git a/blog/feed.xml b/blog/feed.xml
@@ -92,7 +92,7 @@ Brent for his guidance.&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;In late 2018, in the midst of being acquired by Microsoft, GitHub &lt;a href=&quot;https://github.blog/2018-10-16-future-of-software/&quot;&gt;launched Github Actions&lt;/a&gt; into public beta, allowing users to run code on the popular development platform for the first time. With a straightforward &lt;code&gt;YAML&lt;/code&gt; configuration syntax and the power of Microsoft's Azure cloud, GitHub Actions quickly rose to compete with existing Continuous Integration (CI) and Continuous Deployment (CD) platforms like &lt;strong&gt;Circle CI&lt;/strong&gt; and &lt;strong&gt;Travis CI&lt;/strong&gt;. GitHub Actions made it easier than ever for developers to test and deploy software in the cloud, but from the beginning GitHub had bigger plans for the service.&lt;/p&gt;
 &lt;p&gt;In a &lt;a href=&quot;https://techcrunch.com/2018/10/16/github-launches-actions-its-workflow-automation-tool/&quot;&gt;2018 TechCrunch interview&lt;/a&gt;, GitHub's then head of platform acknowledged the usefulness of actions for more than CI/CD. &quot;I see CI/CD as one narrow use case of actions. It’s so, so much more,” Lambert stressed. “And I think it’s going to revolutionize DevOps because people are now going to build best in breed deployment workflows for specific applications and frameworks, and those become the de facto standard shared on GitHub. […] It’s going to do everything we did for open source again for the DevOps space and for all those different parts of that workflow ecosystem.&quot;&lt;/p&gt;
-&lt;p&gt;At Creative Commons, we use Github Actions and Bots on many of &lt;a href=&quot;https://github.com/creativecommons?type=source&quot;&gt;our open-source projects&lt;/a&gt; for more than CI/CD—to manage our &lt;a href=&quot;http://localhost:5000/community/community-team/&quot;&gt;community team&lt;/a&gt;; to automate repository health; and to automate tedious but frequent tasks. The following examples are just a small snapshot of our existing and in-progress automations.&lt;/p&gt;
+&lt;p&gt;At Creative Commons, we use Github Actions and Bots on many of &lt;a href=&quot;https://github.com/creativecommons?type=source&quot;&gt;our open-source projects&lt;/a&gt; for more than CI/CD—to manage our &lt;a href=&quot;/community/community-team/&quot;&gt;community team&lt;/a&gt;; to automate repository health; and to automate tedious but frequent tasks. The following examples are just a small snapshot of our existing and in-progress automations.&lt;/p&gt;
 &lt;h2 id=&quot;example-automations&quot;&gt;Example automations&lt;/h2&gt;&lt;p&gt;&lt;!-- no toc --&gt;&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href=&quot;/blog/entries/automate-github-for-more-than-CI CD/#automatic-release-note-generation&quot;&gt;Release note generation&lt;/a&gt;&lt;/li&gt;
