Start with version history
Git records snapshots of changes in a repository. A commit should represent a coherent change with a message that explains its purpose. Review what is staged before you commit.
Keep private configuration private
Do not commit passwords, API keys or environment files. Use an ignore file for local configuration and document the variable names separately without real values. If a secret has been committed, removing the file alone does not erase its history.
Use a branch for a focused change
A branch lets you work on a change independently. Make small commits, check the result and review the difference before merging. GitHub can host the repository and provide pull requests for that review.
A repository is not a deployment
Uploading code does not automatically put your website online. Deployment is a separate step that moves the intended version into the right running environment. Document how those steps connect.