<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing code is life</title><link>https://arkord.de/</link><description>Recent content on Writing code is life</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 17 Mar 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://arkord.de/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub migration tools reimagined</title><link>https://arkord.de/posts/github-migration-tools-reimagined/</link><pubDate>Tue, 17 Mar 2026 08:00:00 +0200</pubDate><guid>https://arkord.de/posts/github-migration-tools-reimagined/</guid><description>&lt;p&gt;In the last post I wrote about the &lt;a href="https://arkord.de/posts/state-of-github-migration-tools/"&gt;&amp;ldquo;State of GitHub migration tools&amp;rdquo;&lt;/a&gt;. I this post I would like to present my humble attempt to unify and improve the developer experience regarding the GitHub migration tools.&lt;/p&gt;</description></item><item><title>State of GitHub migration tools</title><link>https://arkord.de/posts/state-of-github-migration-tools/</link><pubDate>Mon, 16 Mar 2026 18:00:00 +0200</pubDate><guid>https://arkord.de/posts/state-of-github-migration-tools/</guid><description>&lt;p&gt;For some time I am working on migration projects from various platforms to GitHub. What I soon realized is the miserable state of the GitHub migration tools. It is easy to complain when you&amp;rsquo;re not involved in the development process and don&amp;rsquo;t know the priorities and decisions. Therefore, I would like to outline the current state of the migration tools and what we maybe can do better.&lt;/p&gt;</description></item><item><title>GitHub CLI Extension Template</title><link>https://arkord.de/posts/github-cli-extension-template/</link><pubDate>Fri, 07 Nov 2025 00:00:00 +0200</pubDate><guid>https://arkord.de/posts/github-cli-extension-template/</guid><description>&lt;p&gt;Based on the &lt;a href="https://github.com/github/gh-gei"&gt;gei&lt;/a&gt; project I created a &lt;a href="https://github.com/akordowski/gh-hello"&gt;GitHub CLI extension template project&lt;/a&gt; for dotnet/C#. This templates comes with a GitHub Actions workflow for build, test and publish the extension out of the box.&lt;/p&gt;</description></item><item><title>gl2gh GitHub CLI Extension</title><link>https://arkord.de/posts/gitlab-to-github-migration/</link><pubDate>Wed, 29 Oct 2025 00:00:00 +0200</pubDate><guid>https://arkord.de/posts/gitlab-to-github-migration/</guid><description>&lt;p&gt;I am working for some time now on a migration project from plattforms like Azure DevOps, Bitbucket and GitLab to GitHub Enterprise. There are official &lt;a href="https://cli.github.com"&gt;GitHub CLI&lt;/a&gt; extensions for the migration from Azure DevOps (&lt;a href="https://github.com/github/gh-ado2gh"&gt;ado2gh&lt;/a&gt;) and Bitbucket (&lt;a href="https://github.com/github/gh-bbs2gh"&gt;bbs2gh&lt;/a&gt;) to GitHub but unfortunately none for the migration from GitLab to GitHub.&lt;/p&gt;
&lt;p&gt;For this case I created based on the GitHub Enterprise Importer (&lt;a href="https://github.com/github/gh-gei"&gt;gei&lt;/a&gt;) CLI extension the unofficial &lt;a href="https://github.com/akordowski/gh-gl2gh"&gt;gl2gh&lt;/a&gt; CLI extension. This extension is based on the same code as the other extensions. The code you can find &lt;a href="https://github.com/akordowski/gh-gei/tree/feature/gl2gh"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>GitHub Certifications</title><link>https://arkord.de/posts/github-certifications/</link><pubDate>Thu, 12 Dec 2024 12:00:00 +0200</pubDate><guid>https://arkord.de/posts/github-certifications/</guid><description>&lt;p&gt;After weeks of preperation and exams I finished today my certification for &lt;a href="https://www.credly.com/badges/dca49898-11f6-456c-9ddf-09396383055e/public_url"&gt;GitHub Foundations&lt;/a&gt;, &lt;a href="https://www.credly.com/badges/5e26e396-92c6-4dcb-a9f2-fa6f87229b99/public_url"&gt;GitHub Advanced Security&lt;/a&gt;, &lt;a href="https://www.credly.com/badges/3750b88e-07eb-4a34-b053-476aec5da1f9/public_url"&gt;GitHub Administration&lt;/a&gt; and &lt;a href="https://www.credly.com/badges/2e54a8ee-f221-4350-bb9d-50591fb2bc29/public_url"&gt;GitHub Actions&lt;/a&gt; &amp;#x1f973; &amp;#x1f389;&lt;/p&gt;
&lt;p&gt;
&lt;a href="https://arkord.de/posts/github-certifications/certificates.png" data-dimbox data-dimbox-caption="GitHub Certificates"&gt;
&lt;img alt="GitHub Certificates" src="https://arkord.de/posts/github-certifications/certificates.png"/&gt;
&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Using Semantic Kernel with multiple services</title><link>https://arkord.de/posts/using-semantic-kernel-with-multiple-services/</link><pubDate>Mon, 09 Sep 2024 06:30:00 +0200</pubDate><guid>https://arkord.de/posts/using-semantic-kernel-with-multiple-services/</guid><description>&lt;p&gt;The builder for the &lt;strong&gt;Semantic Kernel&lt;/strong&gt; (SK) allows to add multiple services to the kernel. &lt;a href="https://github.com/microsoft/semantic-kernel/discussions/6375"&gt;I was wondering&lt;/a&gt; how the SK knows which service to choose during the runtime. The answer is quite simple.&lt;/p&gt;</description></item><item><title>Project Server Resources</title><link>https://arkord.de/posts/project-server-resources/</link><pubDate>Sat, 15 Jun 2019 09:00:00 +0200</pubDate><guid>https://arkord.de/posts/project-server-resources/</guid><description>&lt;p&gt;While working with the Project Server I had to search a lot for resources. So I collected them together to have a quick access. I added also &lt;a href="https://www.getpostman.com"&gt;Postman&lt;/a&gt; collections and environments to have a convenient way to test and work with the Project Server REST and OData API. All the resources you can find in the &lt;a href="https://github.com/akordowski/Project-Server-Resources/"&gt;Project Server Resources&lt;/a&gt; repository on GitHub.&lt;/p&gt;</description></item><item><title>Lessons learned from working with Project Server API</title><link>https://arkord.de/posts/lessons-learned-from-working-with-project-server-api/</link><pubDate>Sat, 15 Jun 2019 08:00:00 +0200</pubDate><guid>https://arkord.de/posts/lessons-learned-from-working-with-project-server-api/</guid><description>&lt;p&gt;Recently I worked on a project involving the Microsoft Project Server 2013. My task was to create a data synchronization using the available Project Server API&amp;rsquo;s. I never worked with the Project Server before, so this was all new to me. The way to reach the goal was bumpy and sometimes frustrating. But at the end I learned much during this project, so I would like to share it with you.&lt;/p&gt;</description></item></channel></rss>