git-next/justfile

install-hooks:
  @echo "Installing git hooks"
  cargo install cc-cli
  git config core.hooksPath .git-hooks

validate-dev-branch:
  git rebase -i origin/main -x 'cargo fmt --check'
  git rebase -i origin/main -x 'cargo build'
  git rebase -i origin/main -x 'cargo test'
  git rebase -i origin/main -x 'cargo clippy'

start-ngrok:
  #!/usr/bin/env bash
  # Uses NGROK_DOMAIN env var if available
  if test -z ${NGROK_DOMAIN} ; then
    ngrok http 8080
  else
    ngrok http --domain=${NGROK_DOMAIN} 8080
  fi

coverage-update:
  cargo tarpaulin --lib --out html
  echo "Now:\n\topen tarpaulin-report.html"

coverage crate test:
  cargo tarpaulin -p {{crate}} --lib --out html -- {{test}}
  # cargo tarpaulin --skip-clean -p {{crate}} --lib --out html -- {{test}}
  
grcov-coverage:
  #!/usr/bin/env bash
  set -e
  # an alternate coverage report
  rustup component add llvm-tools-preview
  export RUSTFLAGS="-Cinstrument-coverage"
  cargo build
  export LLVM_PROFILE_FILE="git-next-%p-%m.profraw"
  cargo test
  echo "Building report..."
  grcov . -s . --binary-path ./target/debug/ -t html --branch --ignore-not-existing -o ./target/debug/coverage/
  find . -name '*.profraw' -exec rm "{}" \;
  echo "Now:\n\topen target/debug/coverage/index.html"

publish version:
  #!/usr/bin/bash -e
  [[ -z $(git status --short) ]] || echo "Worktree is Dirty - aborting" ; exit
  echo "Clean"
  git co v{{version}}
  ORDER=$(cargo publish-workspace --target-version {{version}} --crate-prefix git-next --show-order 2>/dev/null | cut -d\  -f2-)
  # INFO: Why not use publish-workspace to publish? It doesn't support when crates-io registry is replaced
  for P in ${ORDER}
  do
    cargo publish --registry crates-io -p $P
  done