move shellcheck.files up
This commit is contained in:
Kay Marquardt (Gnadelwartz)
parent
fd4dd8c432
commit
41b8e6918d
|
|
@ -1,5 +1,5 @@
|
|||
#!/usr/bin/env bash
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
# magic to ensure that we're always inside the root of our application,
|
||||
# no matter from which directory we'll run script
|
||||
|
|
@ -28,8 +28,8 @@ else
|
|||
fi
|
||||
|
||||
# run shellcheck before commit
|
||||
echo "read files from ${HOOKDIR}/shellcheck.files ..."
|
||||
FILES=$(sed '/^#/d' <"${HOOKDIR}/shellcheck.files")
|
||||
echo "read files from dev/shellcheck.files ..."
|
||||
FILES=$(sed '/^#/d' <"dev/shellcheck.files")
|
||||
if [ "$FILES" != "" ]; then
|
||||
# shellcheck disable=SC2086
|
||||
shellcheck -x ${FILES} || exit 1
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
#!/usr/bin/env bash
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
# magic to ensure that we're always inside the root of our application,
|
||||
# no matter from which directory we'll run script
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
#!/usr/bin/env bash
|
||||
# this has to run once atfer git clone
|
||||
# and every time we create new hooks
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
# magic to ensure that we're always inside the root of our application,
|
||||
# no matter from which directory we'll run script
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
# list of files to run shellscheck against
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
# main files
|
||||
bashbot.sh
|
||||
commands.sh
|
||||
bashbot.rc
|
||||
# example files
|
||||
examples/calc
|
||||
examples/notify
|
||||
examples/question
|
||||
examples/calc.sh
|
||||
examples/notify.sh
|
||||
examples/question.sh
|
||||
# dev files
|
||||
dev/version.sh
|
||||
dev/install-hooks.sh
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
#!/bin/bash
|
||||
#
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
# shellcheck disable=SC2016
|
||||
#
|
||||
# Easy Versioning in git:
|
||||
|
|
|
|||
|
|
@ -61,5 +61,5 @@ group. This step is up to you actually.
|
|||
|
||||
#### [Next Getting started](2_usage.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
|
|
@ -159,5 +159,5 @@ send_action "${CHAT[ID]}" "action"
|
|||
#### [Prev Create Bot](1_firstbot.md)
|
||||
#### [Next Advanced Usage](3_advanced.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
|
|
@ -156,5 +156,5 @@ answer_inline_query "$iQUERY_ID" "cached_sticker" "identifier for the sticker"
|
|||
#### [Prev Advanced Usage](3_advanced.md)
|
||||
#### [Next Expert Use](4_expert.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
|
|
@ -104,5 +104,5 @@ An example crontab is provided in ```examples/bashbot.cron```.
|
|||
#### [Prev Expert Use](4_expert.md)
|
||||
#### [Next Best Practice](5_practice.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
|
|
@ -112,5 +112,5 @@ The second warning is about an unused variable, this is true because in our exam
|
|||
#### [Prev Best Practice](5_practice.md)
|
||||
#### [Next Functions Reference](6_reference.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
|
|
@ -348,5 +348,5 @@ Send Input from Telegram to waiting Interactive Chat.
|
|||
#### [Prev Best Practice](5_practice.md)
|
||||
#### [Next Developer Rules](7_develop.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
|
|
@ -28,10 +28,10 @@ If you actived git hooks in Setup step 6, 'version.sh' updates the version name
|
|||
|
||||
For a shell script running as a service it's important to be paranoid about quoting, globbing and other common problems. So it's a must to run shellchek on all shell scripts before you commit a change. this is automated by a git hook activated in Setup step 6.
|
||||
|
||||
In addition you can run ```dev/hooks/pre-commit.sh``` every time you want to shellcheck all files given in 'dev/hooks/shellcheck.files'.
|
||||
In addition you can run ```dev/hooks/pre-commit.sh``` every time you want to shellcheck all files given in 'dev/shellcheck.files'.
|
||||
|
||||
|
||||
#### [Prev Function Reference](6_function.md)
|
||||
|
||||
#### $$VERSION$$ v0.61-0-g3b17bc2
|
||||
#### $$VERSION$$ v0.61-2-gfd4dd8c
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue