Should agents artifacts be committed alongside the code? #421
-
|
For example, the folder |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey @thiagocaiubi, great question! Generally no — agent-generated artifacts (like They're session-specific outputs, so each developer's agent sessions will produce different artifacts based on their context. Not really meant to be shared via version control. Something like this in your The one exception: if your team decides certain generated artifacts (like C4 architecture docs from Hope that helps! |
Beta Was this translation helpful? Give feedback.
Hey @thiagocaiubi, great question! Generally no — agent-generated artifacts (like
.ui-designer/reviews/, temporary analysis files, etc.) are ephemeral working files and should be added to your.gitignore.They're session-specific outputs, so each developer's agent sessions will produce different artifacts based on their context. Not really meant to be shared via version control.
Something like this in your
.gitignoreshould do the trick:The one exception: if your team decides certain generated artifacts (like C4 architecture docs from
/c4-architecture:c4-architecture) are valuable enough to keep as shared documentation — that's totally a v…