~/.local/bin/abra is a symlink to the downloaded abra script, but not a git checkout
Or if we run abra from the checkout, not using a symlink
But neither of these situations is likely gonna be that common.
In the simple case:
$ abra version
0.5.0-23c8521
Whaddya reck?
Closes #100
This isn't perfect, because it'll blow up if:
1. `~/.local/bin/abra` is a symlink to the downloaded `abra` script, but not a git checkout
2. Or if we run abra from the checkout, not using a symlink
But neither of these situations is likely gonna be that common.
In the simple case:
```
$ abra version
0.5.0-23c8521
```
Whaddya reck?
Or if we run abra from the checkout, not using a symlink
Wanna update the README to remove the hacking tip that says just run ./abra? I think this is fine since we give clear guidelines how to get hacking on it (just use --dev)
Nice! LGTM!
> Or if we run abra from the checkout, not using a symlink
Wanna update the README to remove the hacking tip that says just run `./abra`? I think this is fine since we give clear guidelines how to get hacking on it (just use `--dev`)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #100
This isn't perfect, because it'll blow up if:
~/.local/bin/abrais a symlink to the downloadedabrascript, but not a git checkoutBut neither of these situations is likely gonna be that common.
In the simple case:
Whaddya reck?
versionoutput 8b4141670cNice! LGTM!
Wanna update the README to remove the hacking tip that says just run
./abra? I think this is fine since we give clear guidelines how to get hacking on it (just use--dev)