The Challenge: Safe automation without surprises

You have a repository initializer — scripts/git_init.sh — that supports interactive prompts and programmatic --headless invocations. This quest will guide you through validating the script’s behavior, adding tests, and ensuring it behaves well in CI.

Why this matters:

• Scripts are often used in automation and CI; they must behave predictably and be testable.
• Headless behavior must be non-destructive and reliable; interactive commands can’t be used in CI loops.
• Creating files via programmatic scaffolding must be done with a clear contract and test coverage.

🎯 Quest Objectives

By the end of this quest, you will be able to:

• Verify script syntax with bash -n and lint with shellcheck.
• Add Bats tests to confirm --headless operations do not push.
• Ensure it is easy to run --no-push for local tests.
• Add CI step instructions for running tests.

Tests and Tools

We suggest two layers of tests:

1. Unit-ish validations using local filesystem checks via bats.
2. Linting static validation with shellcheck.

Example Bats Test (save in tests/bats/test_headless.bats)

#!/usr/bin/env bats

setup() {
  TMPDIR=$(mktemp -d)
  cd "$TMPDIR"
}

teardown() {
  rm -rf "$TMPDIR"
}

@test "headless mode creates a repo and does not push" {
  run bash "$BATS_TEST_DIRNAME/../../scripts/git_init.sh" --headless -n sample-test --no-push
  [ "$status" -eq 0 ]
  [ -d "$HOME/github/sample-test/.git" ]
}

ShellCheck linting

Install with brew install shellcheck on macOS, or sudo apt-get install -y shellcheck on Linux (Ubuntu / GitHub Actions runners), then run shellcheck scripts/git_init.sh.

Syntax check

Use bash -n scripts/git_init.sh to detect syntax issues early.

Try it locally

Get the script first. Every command below expects scripts/git_init.sh to exist in your working directory. It ships in the IT-Journey repository — clone it (or download the single file) before running anything else:

git clone https://github.com/bamr87/it-journey.git
cd it-journey
# the initializer lives at scripts/git_init.sh
chmod +x scripts/git_init.sh

1. Syntax check

bash -n scripts/git_init.sh

1. Run headless mode locally without pushing

bash scripts/git_init.sh --headless -n test-quest-sample --no-push --gitignore python,macos --scaffold python

1. Run Bats tests

# install bats-core (macOS)
brew install bats-core
# install bats-core (Linux / Ubuntu, e.g. GitHub Actions runners)
sudo apt-get update && sudo apt-get install -y bats

bats tests/bats

1. Run ShellCheck

# macOS
brew install shellcheck
# Linux / Ubuntu (e.g. GitHub Actions runners)
sudo apt-get install -y shellcheck

shellcheck scripts/git_init.sh

Acceptance Criteria

• bash -n returns no error
• shellcheck returns no major errors
• bats tests/bats/test_headless.bats returns pass for headless creation
• --gitignore creates a .gitignore file when requested
• --scaffold python creates src and tests
• --dry-run prints operations and does not create files or push

Next Steps (Optional)

• Try --dry-run to preview changes without applying them.
• Create a GitHub Actions job that installs bats and shellcheck and runs tests on PRs.

Complete this quest to prove you can safely add features to a script and make it testable in automation.

Good luck! 🛠️

🕸️ Knowledge Graph

Structured wiki-links connect this quest to the IT-Journey knowledge graph. Open the Obsidian Graph View to explore connections.

Level hub: [[Level 001 - Journeyman Challenges]] Overworld: [[🏰 Overworld - Master Quest Map]] Obsidian docs: [[Obsidian Knowledge Graph and Wiki Links]]