- [x] command mapping `*coreutils` to `gnu_coreutils`
- [x] ✅ add test for gnu_coreutils
- [x] 💚 add archiving packages to travis
- [x] ✅ add test for archiving commands
* [SC2196] Use grep -Eegrep is non-standard and deprecated.
* [SC2086] Double quoting
Double quote to prevent globbing and word splitting.
* [SC2059] printf syntax
Don't use variables in the printf format string.
Use printf "..%s.." "$foo".
Update matching test to not assume whitespace is <space>
* [SC2002] Useless cat.
Consider 'cmd < file | ..' or 'cmd file | ..' instead.
* Update Unicode PASS/FAIL output
- [x] NEW variables for 'checkmark' and 'fancy x' and tput colours
- [x] eg: `checkmark` = `\342\234\223`
- [x] eg: `PASS=${txtbold}${txtgreen}${checkmark}${txtreset}`
- [x] update `printf` statements to use `%b` for unicode variables.
- [x] Using readonly variables for
- [x] $BINARY_NAME and $VERSION
- [x] $PASS and $FAIL
- [x] refactor `.hasrc` file reading
- [x] [SC2002] Useless cat
- [x] Add new BATS tests for Unicode output
* Repo scaffolding - shellscript filetype
- [x] Add shellscripts to `.editorconfig`
- [x] Add shellscripts to `.gitattributes`
* Refactored tests to use consistent unicode glyphs.
Details:
* Freshen Makefile and update README.md
- [x] Add `sudo` to revelvant commands
- [x] Use named languages (bash) in fenced codeblocks
- [x] Use `console` in fenced codeblocks for command output
- [x] Use `install` with permission mode
The permissions on `has` were 777 from `git clone`.
- [x] Add option to use $PREFIX
What if I don't want to install to /usr/local/bin?
`make PREFIX=$HOME/.local install` now works.
- [x] Add `update` target for `git pull`
- [x] Include .PHONY targets
* Freshen Makefile and update README.md
- [x] Add `sudo` to revelvant commands
- [x] Use named languages (bash) in fenced codeblocks
- [x] Use `console` in fenced codeblocks for command output
- [x] Use `install` with permissions set
The permissions on `has` were 777 from `git clone`.
- [x] Add option to use $PREFIX
What if I don't want to install to /usr/local/bin?
`make PREFIX=$HOME/.local install` now works.
- [x] Add `update` target for `git pull`
- [x] Include .PHONY targets
- [x] Add tests for Makefile changes
- [x] Uses `bats` variables for directories
- ✓ make install creates a valid installation
- ✓ ..even if has is missing from directory
- ✓ make update runs git pull
* Update .hastest.bats
temp remove "git pull" check.
* Update travis to use bats-core 1.10
Do not be concerned about dirty working tree when running make update.
* Change version output to non-blinking.
* Update travis to use bats-core 1.10
Do not be concerned about dirty working tree when running make update.
* Working makefile
* Use `[[` and `@` for the $lines match.
* `make install` MacOS friendly again
Support Colors #12
* added: colors
No more echo with variables in them. Think of it like the Holocaust... Never. Again.
* update: removed color codes from tests
Adds a badge showing the number of people helping this repo on CodeTriage.
[![Open Source Helpers](https://www.codetriage.com/kdabir/has/badges/users.svg)](https://www.codetriage.com/kdabir/has)
## What is CodeTriage?
CodeTriage is an Open Source app that is designed to make contributing to Open Source projects easier. It works by sending subscribers a few open issues in their inbox. If subscribers get busy, there is an algorithm that backs off issue load so they do not get overwhelmed
[Read more about the CodeTriage project](https://www.codetriage.com/what).
## Why am I getting this PR?
Your project was picked by the human, @schneems. They selected it from the projects submitted to https://www.codetriage.com and hand edited the PR. How did your project get added to [CodeTriage](https://www.codetriage.com/what)? Roughly 4 months ago, [@kdabir](https://github.com/kdabir) added this project to CodeTriage in order to start contributing.
## What does adding a badge accomplish?
Adding a badge invites people to help contribute to your project. It also lets developers know that others are invested in the longterm success and maintainability of the project.
You can see an example of a CodeTriage badge on these popular OSS READMEs:
- [![](https://www.codetriage.com/rails/rails/badges/users.svg)](https://www.codetriage.com/rails/rails) https://github.com/rails/rails
- [![](https://www.codetriage.com/crystal-lang/crystal/badges/users.svg)](https://www.codetriage.com/crystal-lang/crystal) https://github.com/crystal-lang/crystal
## Have a question or comment?
While I am a bot, this PR was manually reviewed and monitored by a human - @schneems. My job is writing commit messages and handling PR logistics.
If you have any questions, you can reply back to this PR and they will be answered by @schneems. If you do not want a badge right now, no worries, close the PR, you will not hear from me again.
Thanks for making your project Open Source! Any feedback is greatly appreciated.