is_affected

A utility for checking and listing the affected resources across a range of commits, useful when working with monorepos.

Content

• Usage

  • Usage - Git Environment Variables
  • Usage - Logging

• CICD Examples

  • GitHub Actions
  • GitLab CI

• Downloading Binary

• Compiling via Local Repository

• Compiling via Cargo

• Unit Testing

• End-to-End Testing

• Issues/Feature Requests

Usage

Is Affected operates upon a range of Git commits in the repositories' history. To specify the range of commits you can use either the --from-commit-hash <commit-hash> or --from-reference <reference> arguments. The range of commits starts exclusively from the commit specified till inclusively of HEAD. One of these from arguments are required, but they conflict and can not be used together.

Over the range of commits you can perform two possible operations. Either you can list all the affected resources by supplying the --list flag. Or you can check that specific resources have been affected, through the --affects-current-directory flag or the --affects <resources> argument. With the --affects-current-directory flag the affected resources are checked if they are within the current directory or sub-directories. Using the --affects <resource> argument you can supply multiple regexes and it is checked if any of the affected resources match any. If either of the affects checks are met then Is Affected return a zero status code, otherwise it return a non-zero status code. One of the output arguments are required, but they conflict and can not be used together.

Usage - Git Environment Variables

When looking for a repository the Git environment variables are respected. When ${GIT_DIR} is set, it takes precedence and Is affected begins searching for a repository in the directory specified in ${GIT_DIR}. When ${GIT_DIR} is not set, Is Affected searches for a repository beginning in the current directory.

Usage - Logging

The crates pretty_env_logger and log are used to provide logging. The environment variable RUST_LOG can be used to set the logging level. See https://crates.io/crates/pretty_env_logger for more detailed documentation.

CICD Examples

All CI examples set up the environment and then execute a script to perform the action. This approach is recommended as it allows us to avoid provider-specific quirks and constraints, while also enabling us to execute the same logic locally. It also enables the use of tools such as formatter and linters, ensuring consistency and reducing errors compared to embedding commands directly into the CI provider's custom syntax.

GitHub Actions

name: Example

on: pull_request

jobs:
  example:
    runs-on: ubuntu-latest
    container:
      image: rust
    steps:
      - name: Checkout code.
        uses: actions/checkout@v3
        # https://github.com/actions/checkout
        # Checks out only a single merge commit of the pull request and the target branch by default.
        with:
          ref: ${{ github.event.pull_request.head.sha }}
          fetch-depth: 0
      - name: Install is_affected.
        # Installation options
        # https://github.com/DeveloperC286/is_affected/tree/main/is_affected#downloading-binary
        # https://github.com/DeveloperC286/is_affected/tree/main/is_affected#compiling-via-cargo
        run: cargo install is_affected --version ^0
      - name: Example is_affected usage.
        run: ci/example.sh

#!/usr/bin/env sh

set -o errexit
set -o xtrace

# https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/variables
target="origin/${GITHUB_BASE_REF}"

# Only act if the directory 'frontend/' is affected in the merge/pull request.
if is_affected --from-reference "${target}" --affects "frontend/"; then
	echo "..."
fi

GitLab CI

example:
  image: rust
  before_script:
    # Installation options
    # https://github.com/DeveloperC286/is_affected/tree/main/is_affected#downloading-binary
    # https://github.com/DeveloperC286/is_affected/tree/main/is_affected#compiling-via-cargo
    - cargo install is_affected --version ^0
  script:
    - ci/example.sh
  rules:
    - if: $CI_MERGE_REQUEST_ID

#!/usr/bin/env sh

set -o errexit
set -o xtrace

# https://docs.gitlab.com/ee/ci/variables/predefined_variables.html
target="origin/${CI_MERGE_REQUEST_TARGET_BRANCH_NAME}"

# Only act if the directory 'frontend/' is affected in the merge/pull request.
if is_affected --from-reference "${target}" --affects "frontend/"; then
	echo "..."
fi

Downloading Binary

Statically linked compiled binaries are available for download. Visit the releases page at https:///github.com/DeveloperC286/is_affected/releases to see all the releases, the release notes contains links to binary downloads for various architectures.

If you do not trust the provided binaries another option is to compile your own and then make it available for remote download, so your CICD etc can then download it.

Compiling via Local Repository

Checkout the code repository locally, change into the repository's directory and then build via Cargo. Using the --release flag produces an optimised binary but takes longer to compile.

git clone git@github.com:DeveloperC286/is_affected.git
cd is_affected/
cargo build --release

The compiled binary is present at target/release/is_affected.

Compiling via Cargo

Cargo is the Rust package manager, the install sub-command pulls from crates.io and then compiles the binary locally, placing the compiled binary at ${HOME}/.cargo/bin/is_affected.

cargo install is_affected

By default it installs the latest version at the time of execution. You can specify a specific version to install using the --version argument. For certain environments such as CICD etc you may want to pin the version.

e.g.

cargo install is_affected --version 0.4.2

Rather than pinning to a specific version you can specify the major or minor version.

e.g.

cargo install is_affected --version ^0

Will download the latest 0.* release whether that is 0.4.2 or 0.7.0.

Unit Testing

The unit test suite has several parameterised tests, Cargo is used to set up and run all the unit tests.

cargo test

End-to-End Testing

To ensure correctness as there are a variety of out of process dependencies the project has an End-to-End behaviour driven test suite using the behave framework (https://github.com/behave/behave).

To run the test suite you need to

• Compile the Is Affected binary.
• Install Python3.
• Install Behave.
• Execute Behave.

Note - You can't use --release as the test suite uses target/debug/is_affected.

cargo build
cd is_affected/end-to-end-tests/
virtualenv -p python3 .venv
source .venv/bin/activate
pip3 install -r requirements.txt
behave

Issues/Feature Requests

To report an issue or request a new feature use https://github.com/DeveloperC286/is_affected/issues.