While we already have a git dependency type, this has pretty heavy overhead, either requiring you to have git installed, or to bootstrap git outside of this process. In some cases, this is an unrealistic expectation.
On the other hand, while we have a FileDownload dependency type, this doesn't account for the post-download operations (extracting archive, resulting folder name including the branch, etc.), which should ideally be abstracted out.
@dfinke Recently wrote a handy function to simplify installing a module from a GitHub repo. We'll borrow ideas and a little code from this. Additionally, we'll borrow BuildHelpers code to help identify PowerShell modules under a particular path, to accommodate repos that have module files at the root of the repo, in a nested folder, etc.
Down the line, I could see this being the default dependency type for simple syntax including a single '/', where full git urls would continue defaulting to the git dependency type.
While we already have a git dependency type, this has pretty heavy overhead, either requiring you to have git installed, or to bootstrap git outside of this process. In some cases, this is an unrealistic expectation.
On the other hand, while we have a FileDownload dependency type, this doesn't account for the post-download operations (extracting archive, resulting folder name including the branch, etc.), which should ideally be abstracted out.
@dfinke Recently wrote a handy function to simplify installing a module from a GitHub repo. We'll borrow ideas and a little code from this. Additionally, we'll borrow BuildHelpers code to help identify PowerShell modules under a particular path, to accommodate repos that have module files at the root of the repo, in a nested folder, etc.
Down the line, I could see this being the default dependency type for simple syntax including a single '/', where full git urls would continue defaulting to the git dependency type.