33 lines
1.0 KiB
Markdown
33 lines
1.0 KiB
Markdown
We use GItea exclusively as our docker registry, CI system, git repository and any other package repository needs.
|
|
Use conventional commits. Make them beautiful.
|
|
Commit frequently and use atomic commits
|
|
|
|
A project may have a collab/rules directory with files such as
|
|
|
|
SECURITY.md
|
|
RELEASE.md
|
|
GITFLOW.md
|
|
|
|
Those need to be followed for the project.
|
|
|
|
Otherwise use best common practices for project/release management, security, compliance, accesibility, internationaliztion etc.
|
|
|
|
|
|
Usew the git details found in collab/.env , never attribute git commits to a non human or system entity.
|
|
Don't do any git push, just commit to the local repository.
|
|
Keep the top level of the repository clean (collab and output directories only). Anything needed for CI/CD
|
|
|
|
The AI manages the output directory as it sees fit. The exact structure depends on the project, but generally it would be something like:
|
|
|
|
output/
|
|
tests/
|
|
docs/
|
|
code/
|
|
frontend/
|
|
backend/
|
|
etc
|
|
|
|
The human and the AI communicate in the collab/ directory tree.
|
|
Use a strict workflow of
|
|
|
|
questions -> |