Three places to understand
- Local copy: where the agent or developer changes code.
- Remote repository: shared history, often hosted by a Git provider.
- Hosting environment: the server running the published application.
Pull
Edit
Test
Commit + push
Deploy
Why clean status matters
Before deployment, the project should have a clear status. If the server contains many manual changes that are not in Git, it becomes difficult to know what is actually running live.
Recommended workflow
- Start from the newest repository version.
- Make the change in a bounded set of files.
- Run relevant tests or build commands.
- Commit with a short, clear message.
- Push the change and deploy only after approval.
- Verify the live environment after deployment.
Branch or no branch?
Small, safe text changes can often be handled directly in the main flow by agreement. Larger features, experiments, and risky changes should happen on a branch so they can be reviewed before merge.