From e6381c65b17a9866250d8ab6ffec2916d8f01f7d Mon Sep 17 00:00:00 2001 From: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com> Date: Fri, 8 Nov 2024 08:14:11 +0000 Subject: [PATCH] Update modified date --- src/pages/docs/projects/version-control/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/docs/projects/version-control/index.md b/src/pages/docs/projects/version-control/index.md index ead86cb89..e37051489 100644 --- a/src/pages/docs/projects/version-control/index.md +++ b/src/pages/docs/projects/version-control/index.md @@ -1,7 +1,7 @@ --- layout: src/layouts/Default.astro pubDate: 2023-01-01 -modDate: 2024-09-17 +modDate: 2024-11-08 title: Configuration as Code description: Projects can be version-controlled as text in a Git repository icon: fa-brands fa-git-alt @@ -71,4 +71,4 @@ Learn more about [creating and deploying releases in a version controlled projec The Configuration as Code feature is designed to give you the benefits of source control, branching, reverting, and pull requests while being able to use your tool of choice to manage your processes (and eventually) variables. While it has many benefits, there are some unsuitable use cases and scenarios. -Learn more about [unsupported config-as-code scenarios](/docs/projects/version-control/unsupported-config-as-code-scenarios) \ No newline at end of file +Learn more about [unsupported config-as-code scenarios](/docs/projects/version-control/unsupported-config-as-code-scenarios)