Skip to content

Commit

Permalink
chore: oh my pre-release v0.1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
is-it-ayush committed Dec 23, 2023
1 parent c7173bf commit 40ffb28
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 4 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ jobs:
runs-on: ubuntu-latest
if: github.event_name == 'release'
strategy:
fail-fast: false
fail-fast: true
matrix:
target: [x86_64-pc-windows-gnu, x86_64-unknown-linux-gnu, x86_64-apple-darwin]
target: [x86_64-pc-windows-gnu, x86_64-unknown-linux-musl, x86_64-apple-darwin]
steps:
- uses: actions/checkout@master
- name: compile and release.
Expand Down
8 changes: 6 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,13 @@ fa -V # print the version

### installation.

wip 🚧
- you need a [gpg](https://gnupg.org/) key & i suggest you [read this blog](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key).
- goto [releases](./releases) and download the one for your platform.
- linux: put it inside /usr/bin/ and run `chmod +x /usr/bin/fa`. assuming /usr/bin is in your `$HOME` variable. you'll get `fa` on your system.
- mac: put it inside the directory where you store your mac binaries (it has to be on path) and grant it perms to execute itself. i'm sorry, i don't own a mac so i don't know this one for sure.
- windows: put it anywhere you like, copy it's location and add it to `$PATH` environment variable.

> sorry! i'm still working on it. i'll release it when it's done and is usable enough.
> if possible! i'll make this easier for future releases.
### configuration.

Expand Down

0 comments on commit 40ffb28

Please sign in to comment.