Integrate git into Claude's development process
This commit is contained in:
parent
6029206d1b
commit
d9d1ef0878
1 changed files with 6 additions and 0 deletions
|
|
@ -85,6 +85,12 @@ command -v -o file.txt
|
|||
|
||||
Long options are self-documenting and make scripts and examples easier to understand without consulting help text. Short options are acceptable for interactive use but should not appear in committed code, documentation, or examples.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
Assume you are working in a git repository. Partition changes into small, self-contained commits and commit each before proceeding to the next change. When enacting a plan, a single action item will often span several such commits — that is expected and preferred over bundling unrelated changes together.
|
||||
|
||||
Leverage the git history during development as well. Git enables efficient and reliable rollbacks of recent changes or research dead ends, and clean reverts of specific diffs from earlier in the history. Prefer these over manual cleanup.
|
||||
|
||||
## Green-Field Project Setup
|
||||
|
||||
When setting up a new project, code-quality and developer-experience tooling must be included from the start and integrated into the development workflow. The principles below use Python as a concrete example, but apply generally to any language ecosystem.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue