<?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 Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/github/</link>
		<description>Recent content in GitHub on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/tags/github/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Why Topic Branches Drive High-Quality Delivery</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</link>
				<pubDate>Mon, 14 Jul 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/</guid>
				<description>Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality.</description>
			</item>
			<item>
				<title>Stop Promoting Branches</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/</link>
				<pubDate>Thu, 06 Feb 2025 09:00:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/</guid>
				<description>Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster.</description>
			</item>
			<item>
				<title>Too many teams overcomplicate their branching strategies</title>
				<link>https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</link>
				<pubDate>Thu, 06 Feb 2025 09:38:01 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/</guid>
				<description>Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability.</description>
			</item>
			<item>
				<title>Open-source with VSTS or TFS and Github for better DevOps</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/</link>
				<pubDate>Tue, 10 May 2016 16:19:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/open-source-with-vsts-or-tfs-and-github-for-better-devops/</guid>
				<description>You can use VSTS or TFS for full DevOps and agile capabilities while keeping your open-source code on Github by setting up automated two-way synchronization between the platforms. This approach lets you manage private work and processes in VSTS, then publish selected branches to Github for public access and contributions. Set up automated builds in VSTS to sync code in both directions, using personal tokens for authentication, so you get the best of both tools without extra manual effort.</description>
			</item>
			<item>
				<title>Migrating from Codeplex to Github</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/migrating-from-codeplex-to-github/</link>
				<pubDate>Wed, 02 Mar 2016 14:29:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/migrating-from-codeplex-to-github/</guid>
				<description>Migrating a Codeplex repository to GitHub is necessary due to declining support and features on Codeplex, but GitHub&amp;rsquo;s import tool is unreliable and does not handle folder selection or branches well. Using Git-TF with Chocolatey provides a more flexible and effective migration, allowing you to select specific folders and preserve history, though some manual steps are needed for wiki pages and other content. Development managers should use Git-TF for smoother migrations and plan for some manual adjustments, especially for documentation.</description>
			</item>
			<item>
				<title>GitHub</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/github/</link>
				<pubDate>Thu, 10 Apr 2025 10:16:54 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/github/</guid>
				<description>GitHub is a comprehensive platform that facilitates version control, collaboration, and integration within software development. Originating as a hosting service for Git repositories, it has evolved to include features such as GitHub Actions for automating continuous integration and continuous delivery workflows, and GitHub Projects for task management and progress tracking. Its significance lies in its ability to enhance collaboration among development teams, reduce friction in development cycles, and support the efficient delivery of value. GitHub is essential for organisations seeking to maintain transparency and integrate workflows between development and operations teams, as its integration with CI/CD practices allows for the automation of testing, builds, and deployments, ensuring continuous validation and delivery of code changes. The platform&amp;rsquo;s features, including issues, pull requests, and discussions, foster effective communication and alignment on project goals. Additionally, GitHub&amp;rsquo;s compatibility with a variety of third-party tools and services further amplifies its effectiveness in modern DevOps environments. By utilising GitHub&amp;rsquo;s extensive toolset, organisations can enhance team collaboration, streamline development processes, and improve software delivery outcomes.</description>
			</item>
	</channel>
</rss>
