The abaco init workflow creates a directory containing various source and configuration files, but the directory itself is not managed by source control. This makes it challenging to use features like tagging with the most recent git commit hash, or (eventually), deploying actors via push to a remote repository rather than directly from the development host.
There are a handful of steps to be added to the abaco init workflow to make this a reality:
Initialize the new directory as a git repository
Add and commit the initial set of files
Script creation of a remote (GitHub, Gitlab, on-prem Gitlab, etc.) and set as upstream for the repository
Optional (and open for discussion): Push the initial commit
Steps 2-4 will be managed in other issues. This issue covers only initialization of the repository.
The
abaco init
workflow creates a directory containing various source and configuration files, but the directory itself is not managed by source control. This makes it challenging to use features like tagging with the most recent git commit hash, or (eventually), deploying actors via push to a remote repository rather than directly from the development host.There are a handful of steps to be added to the
abaco init
workflow to make this a reality:Steps 2-4 will be managed in other issues. This issue covers only initialization of the repository.