<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Version control on phiz</title><link>https://phiz.ca/tags/version-control/</link><description>Recent content in Version control on phiz</description><generator>Hugo</generator><language>en</language><copyright>Powered by [Wellington-Dufferin-Guelph Public Health](https://wdgpublichealth.ca/)</copyright><lastBuildDate>Mon, 04 May 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://phiz.ca/tags/version-control/index.xml" rel="self" type="application/rss+xml"/><item><title>CI/CD: Its Place in Public Health Software Teams</title><link>https://phiz.ca/posts/2026-05-ci-cd-precommit/</link><pubDate>Mon, 04 May 2026 00:00:00 -0400</pubDate><guid>https://phiz.ca/posts/2026-05-ci-cd-precommit/</guid><description/></item><item><title>Innovation in the open</title><link>https://phiz.ca/posts/2025-12-open-source-innovation/</link><pubDate>Wed, 17 Dec 2025 00:00:00 -0500</pubDate><guid>https://phiz.ca/posts/2025-12-open-source-innovation/</guid><description>&lt;p>Open-source is a way to build public health tooling that is portable, auditable, and easier to collaborate on. A commitment to open-source forces us to take best practices in our programming seriously, such as strong documentation and clear separation between code, sensitive data inputs, and system configurations. In the public sector, it allows us to maximize the value of public dollars and offer greater transparency into our processes.&lt;/p></description></item></channel></rss>