Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bringing Section summaries to Git index page #69

Merged
merged 1 commit into from
Jul 18, 2023
Merged

Bringing Section summaries to Git index page #69

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/docs/how-we-work/git/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ Version control is a staple part of the development cycle and it is important we

While there are multiple types of version control systems available, we have defaulted to using git in all cases. It is ubiquitous and the only difference among teams is where the repository is hosted and what kind of branching workflow is followed. At Axelerant, we always use git, mostly work with Github, and encourage trunk-based development workflows.

{{< section-pages >}}

## Feature-branching and multiple environments

The method of branching determines how quickly you are able to begin working on a new feature and complete it. In a GitOps workflow (such as the one we commonly work with when using platform.sh), the branching mechanism also defines what environments are available.
Expand Down
Loading