Skip to content

Commit 46410b7

Browse files
Merge pull request #2519 from OctopusDeploy/team-devex/editing-a-project-with-version-control-enabled
Update Editing A Project With Version Control Enabled
2 parents 186ed7b + 217b200 commit 46410b7

File tree

4 files changed

+4
-3
lines changed

4 files changed

+4
-3
lines changed
43.5 KB
Loading
18.9 KB
Loading
42.2 KB
Loading

src/pages/docs/projects/version-control/editing-a-project-with-version-control-enabled.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
---
22
layout: src/layouts/Default.astro
33
pubDate: 2023-01-01
4-
modDate: 2023-10-04
4+
modDate: 2024-09-17
55
title: Editing a project with version control enabled
66
description: What to expect when using the Configuration as Code feature in Octopus Deploy
7-
navOrder: 30
7+
navOrder: 30
8+
icon: fa-brands fa-git-alt
89
---
910

1011
Once an Octopus Project is configured to be version-controlled, your experience making changes to a project will change. With the configuration as code feature, you can either edit the resources via the Octopus Deploy UI or your favorite file editing tool. This page will walk through what to expect.
@@ -15,7 +16,7 @@ Editing via the Octopus Deploy UI works the same whether you are saving to a git
1516

1617
### Branch switcher
1718

18-
The first difference is the addition of a branch-switcher. When editing the deployment process via the Octopus UI, the branch is selected in the branch-switcher in the left-hand navigation.
19+
The first difference is the addition of a branch-switcher. When editing the deployment process via the Octopus UI, the branch is selected in the branch-switcher at the top of page.
1920

2021
:::figure
2122
![Branch-switcher user-interface](/docs/projects/version-control/branch-switcher-ui.png)

0 commit comments

Comments
 (0)