Git and Repository Setup

This page describes the first-time setup after either a native host installation or a pre-configured VM handover.

Personal Git Identity

Configure the Git author identity for the Windows user:

git config --global user.name "Max Mustermann"
git config --global user.email "max.mustermann@company.com"
git config --global credential.helper manager
git config --global init.defaultBranch main

These settings control commit metadata and credential handling. They do not grant access to the repository.

Repository Access

The repository is currently private on GitHub. Before cloning:

1. Tom Westerling grants the engineer access to the private repository.
2. The engineer accepts the GitHub invitation.
3. The engineer authenticates with the same GitHub account on the VM or host.

Use the browser to verify access before cloning:

https://github.com/tomwesterling/pcs

If GitHub shows a 404 page while logged in as the engineer, the account has not accepted access yet.

Clone

Use the current repository URL:

mkdir $env:USERPROFILE\source
cd $env:USERPROFILE\source
git clone https://github.com/tomwesterling/pcs.git
cd pcs

The first authenticated Git operation may open a browser login through Git Credential Manager.

Open In VS Code

Open the repository folder:

code .

VS Code should offer to install recommended workspace extensions.

Recommended extensions are in Git

The repository contains .vscode/extensions.json, so colleagues receive the same extension recommendations.

If no prompt appears, open the Extensions view and search:

@recommended

Next Step

Continue with Windows Setup (2): PCS Tool Bootstrap. That page runs .\pcs.cmd install tools, initializes the repository-local environment, checks TIA Openness access, and verifies the PCS CLI.