Git & Delivery

Connect source control to infrastructure work. Inspect a repository, choose a branch and coordinate a deployment with explicit destinations and credentials.

Repository inspection

Read status, branches and tracked changes before a modifying operation.

Clone & pull

Use an authorized repository URL and destination. Check local modifications before updating a working tree.

Publish & push

Prepare a scoped project commit and push only to the operator-approved repository and branch.

Credential boundaries

Use configured integration credentials without placing access tokens in chat or project files.

Deployment hand-off

Inspect manifests and requirements after source checkout, then coordinate the web or OS workflow.

Verification

Record commit identity, branch, resulting working-tree state and application verification where relevant.

Workflow

Inspect

Read repository, branch and local modifications.

Scope

Confirm project path, remote and desired branch.

Apply

Run the permitted Git operation.

Verify

Confirm commit and repository state; test deployed applications separately.

Example prompts

@web01 show the Git status and current commit in /srv/app. Do not modify files.

@web01 clone the approved GitLab repository into /srv/app-test and inspect its README and dependency manifests.

@web01 prepare a commit for the project changes, exclude secrets and show the files before pushing to the configured remote.

Evidence

Remote and branch
Files in scope
Commit identity and return codes
Independent deployment/CI evidence if queried

Prerequisites

Git available on the endpoint.
Authorized remote repository and configured credentials.
Explicit branch, project path and policy for existing local changes.

Boundaries

Protected branches, conflicts, missing permissions and private registry access can block a workflow. A push is not proof that CI or the application deployment succeeded.