scubbo/blogcontent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correction to indentation

Browse Source
This commit is contained in:
Jack Jackson 2025-02-25 18:49:04 -08:00
parent b57dc4636d
commit 20b3020b75
1 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
.gitea/workflows/publish.yaml
View File

@ -22,29 +22,29 @@ jobs:
runs-on: busybox runs-on: busybox
steps: steps:
- run: | - run: |
echo "Hello World" echo "Hello World"
# This is necessary because, if `grep ...` doesn't find anything, it will _return_ (not print) a value of 1 # This is necessary because, if `grep ...` doesn't find anything, it will _return_ (not print) a value of 1
# (non-zero return codes indicating errors in Unix - since there are many more ways for something to go wrong # (non-zero return codes indicating errors in Unix - since there are many more ways for something to go wrong
# than there are for it to go right!), and so the `files=` assignment will also return 1, and the whole operation # than there are for it to go right!), and so the `files=` assignment will also return 1, and the whole operation
# will be considered a failure. # will be considered a failure.
# #
# Since a non-zero value is truthy in Linux, we can use the OR operator (`||`) to only execute the second command # Since a non-zero value is truthy in Linux, we can use the OR operator (`||`) to only execute the second command
# if the first one errors out. So, this line can be translated to English as: # if the first one errors out. So, this line can be translated to English as:
# "Set the variable `files` to a list of all the files that contain `TK` - unless there aren't any, in which case # "Set the variable `files` to a list of all the files that contain `TK` - unless there aren't any, in which case
# set it to `FILES NOT FOUND" # set it to `FILES NOT FOUND"
files=$(grep -rl 'TK' blog/content/posts || echo "FILES NOT FOUND") files=$(grep -rl 'TK' blog/content/posts || echo "FILES NOT FOUND")
# We have to filter out (`grep -v`) the "marker" value of `FILES NOT FOUND`, otherwise the no-matches case would # We have to filter out (`grep -v`) the "marker" value of `FILES NOT FOUND`, otherwise the no-matches case would
# be recorded as having 1 matching file, leading to an error-out below. # be recorded as having 1 matching file, leading to an error-out below.
# (I guess _technically_ there's an edge case in that, if I ever make a blog post titled "FILES NOT FOUND" _which also_ # (I guess _technically_ there's an edge case in that, if I ever make a blog post titled "FILES NOT FOUND" _which also_
# contains the string `TK`, it would slip through this check. But that feels pretty unlikely - not least because spaces # contains the string `TK`, it would slip through this check. But that feels pretty unlikely - not least because spaces
# are very rare in my filesystem names - so I'm ok taking that risk) # are very rare in my filesystem names - so I'm ok taking that risk)
count=$(wc -l <(echo "$files" | grep -v "FILES NOT FOUND") | awk '{print $1}') count=$(wc -l <(echo "$files" | grep -v "FILES NOT FOUND") | awk '{print $1}')
if [[ "$count" -gt "0" ]]; then if [[ "$count" -gt "0" ]]; then
echo "Found TK in $count files:" echo "Found TK in $count files:"
echo $files echo $files
exit 1 # TODO - and alerting via Telegram! exit 1 # TODO - and alerting via Telegram!
fi fi
build-blog: build-blog:
depends-on: depends-on: