Closed fregante closed 3 years ago
This also solves one specific scenario explained on https://github.com/Rich-Harris/degit/issues/37#issuecomment-739428160
Any idea when this PR will get merged
@fregante Could you modify the readme of your repo to add installation directions. Now it says npm i -g degit. It should say degitto to make it clear. Also, this might just be an issue for me. But after installing I needed to add shebang #!/usr/bin/env node
in the beginning of bin.js to be able to run it. We should make your fork a community driven fork, since this project has been abandoned.
If anyone would like to maintain a fork, please do. Degitto is meant to be temporary and only fixes this issue. I’ll probably rewrite only the part I need and merge into my GitHub Actions Templating project rather than keep degit/degitto as a dependency.
@fregante @paulocoghi @rajasegar @Rich-Harris I started a community driven fork that has this PR included among other fixes. https://github.com/tiged/tiged I welcome people to star it, if they like it (currently has 1). When or if Rich Harris becomes active again, I am willing to give him control of that repo or merge it to this. In the mean time I am looking for people to maintain this repo. Any help is welcome.
If you want to use the fork. Simply run:
npm uninstall -g degit
npm install -g tiged
Then you can just use it like you used to. degit username/repo my-app
. You don't need to write tiged (it doesn't even work with that name).
Thank you! And apologies for the long delay. Released as 2.8.1
Replaces and closes #235 Replaces and closes #204 Fixes #207 Fixes #37 Fixes #254 Closes #242
The solution is simple if you detach yourself from
master === default
and instead use the HEAD as the right terminology in a remote server.This could alternatively internally referred to as
<default>
instead ofHEAD
, but I like minimal-impact PRs.Also available in the https://github.com/tiged/tiged community fork