-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR to close simple commits #58
Conversation
@@ -1764,6 +1780,7 @@ case $1 in | |||
cabal-new) die "cabal-new is not supported, please use cabal-v2 instead";; | |||
cabal-v2) shift; eval_env "$@"; BUILD=cabal-v2;; | |||
stack) shift; eval_env "$@"; BUILD=stack;; | |||
hlint) shift; eval_env "$@"; BUILD=hlint;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you check all places where "$BUILD" is being used? At many places if it is not cabal build we assume stack build in the else case, now that we have hlint build we should consider that case too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, those cases don't occur because of the final if-else statement. Maybe we could set "$COMMAND" and derive "$BUILD" accordingly.
fi | ||
local sane_ignore_file=".packcheck/sane-ignore" | ||
printf "$pi_files_exist" > "$sane_ignore_file" | ||
cat "$sane_ignore_file" .packcheck/tar-ztf.txt \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a sane_ignore_file? anyway the results will be correct even with the insane one.
Applicable for: - githubci - circleci - travisci
Closes,
Partially closes,