Summary
After partio enable or partio configure modifies .partio/settings.json, print a hint reminding the user to commit the file so that team members share the same configuration.
Why
When users configure team-shared settings (like checkpoint strategy or agent type), forgetting to commit .partio/settings.json means teammates won't pick up those settings. This is especially easy to miss because the file is created/modified by CLI commands rather than edited by hand. A simple hint at the right moment prevents configuration drift across the team.
Source
Target Repos
Acceptance Criteria
Context Hints
cli/cmd/partio/
cli/internal/config/
Comment /minion build or add the minion-approved label to begin implementation.
Summary
After
partio enableorpartio configuremodifies.partio/settings.json, print a hint reminding the user to commit the file so that team members share the same configuration.Why
When users configure team-shared settings (like checkpoint strategy or agent type), forgetting to commit
.partio/settings.jsonmeans teammates won't pick up those settings. This is especially easy to miss because the file is created/modified by CLI commands rather than edited by hand. A simple hint at the right moment prevents configuration drift across the team.Source
entireio-cli-pullsTarget Repos
cliAcceptance Criteria
partio enableorpartio configuremodifies.partio/settings.json, a hint is printed reminding the user to commit the file if it contains team-shared settings.partio/settings.jsonhas uncommitted changes (not when it is already tracked and clean)Context Hints
cli/cmd/partio/cli/internal/config/Comment
/minion buildor add theminion-approvedlabel to begin implementation.