You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we create a kit for a user we don't currently initialise a git repository, that means that most of our users will need to do that for themselves. They're likely to do so after making some of their own changes which will make it harder for them to look back and see what changes they made vs the kit that was generated for them.
Why
It will save users from needing to remember to initialise it themselves, this is something I believe most users would benefit from and there is very little downside for users who don't use the functionality
Who needs to work on this
Developer
Who needs to review this
Developer
Done when
Git is initialised by default with an initial commit
Users can opt-out of git with a flag like --version-control=none
If user doesn't have git installed create still happens successfully
If user has already initialised git repo create still happens successfully, but without commit
The text was updated successfully, but these errors were encountered:
What
When we create a kit for a user we don't currently initialise a git repository, that means that most of our users will need to do that for themselves. They're likely to do so after making some of their own changes which will make it harder for them to look back and see what changes they made vs the kit that was generated for them.
Why
It will save users from needing to remember to initialise it themselves, this is something I believe most users would benefit from and there is very little downside for users who don't use the functionality
Who needs to work on this
Who needs to review this
Done when
--version-control=none
create
still happens successfullycreate
still happens successfully, but without commitThe text was updated successfully, but these errors were encountered: