sanguine

Git Changes Action

This GitHub Action exports a variable that contains the list of Go modules changed in the current pull request, and if desired, along with any dependent modules. This can be useful for automating build, test, or deployment workflows that involve Go projects.

Usage:

1. To use this action, add the following steps to your workflow:

   Check out the current pull request using the actions/checkout action. It’s recommended to set fetch-depth to 0 and submodules to ‘recursive’ to ensure that all necessary dependencies are fetched.

    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
          submodules: 'recursive'
          dependencyLevelResolution: "modules"

1. Use the synapsecns/sanguine/git-changes-action Docker image to run the git-changes script, which exports a variable that contains the list of changed Go modules.

      - uses: docker://ghcr.io/synapsecns/sanguine/git-changes-action:latest
        id: filter_go
        with:
          github_token: $
          timeout: "1m" # optional, defaults to 1m
          dependencyLevelResolution: "modules" 
          # For package level resolution, use "packages" instead of "modules"

You can customize the behavior of the git-changes script by using the following inputs:

• github_token: The token to use for authentication with the GitHub API. This is required to fetch information about the current pull request.
• timeout: The maximum time to wait for the GitHub API to respond. Defaults to 1 minute.
• dependencyLevelResolution: “modules” or “packages”.

The output of the git-changes script is a comma-separated list of Go module paths. You can access this list using the filter_go output variable, like so:

      - run: echo 'Changed modules:' $
      - run: echo 'Unchanged modules:' $
      - run: echo 'Changed modules (including dependencies):' $
      - run: echo 'Unchanged modules (including dependencies):' $

How It Works

First a change tree is calculated between the ref and the base (as passed in by the user or inferred by the event type) based on the flow described below and here. This is a file tree that contains all the files that have changed between two refs.

graph TB
    A(Start) --> B{Check triggering workflow}
    B -- pull request --> C[Calculate a list diff with the GitHub API]
    B -- push --> D{Check base}
    D -- Base same as head --> E[Changes detected against most recent commit]
    D -- Base is a commit sha --> F[Changes detected against the sha]
    C --> G(Generate Chagned File List)
    E --> G
    F --> G

Module Level Resolution

Each module in the go.work is visited. If any changes are detected, the module itself is added to the list of changed modules. By setting include_dependencies to modules, changes to their direct or indirect module dependencies will flag the module as changed. This process is repeated until all modules in the go.work have been visited.

sequenceDiagram
  participant GW as go.work
  participant M as Module
  participant CML as Changed_Module_List
  participant UML as Unchanged_Module_List
  participant D as Dependency

  GW->>M: Visit Module
  Note over M: Check for changes
  M-->>GW: Changes Detected?
  alt Changes Detected
    GW->>CML: Add Module to Changed_Module_List
    M->>D: Has Dependency in go.work?
    alt Has Dependency
      GW->>CML: Add Dependency to Changed_Module_List
    else No Dependency
      M-->>GW: No Dependency to Add
    end
  else No Changes Detected
    GW->>UML: Add Module to Unchanged_Module_List
    M->>D: Has Dependency in go.work?
    alt Has Dependency
      GW->>UML: Add Dependency to Unchanged_Module_List
    else No Dependency
      M-->>GW: No Dependency to Add
    end
  end
  GW->>GW: Continue Until All Modules Visited

Package Level Resolution

Each module in the go.work is visited. If any changes are detected, the module itself is added to the list of changed modules. By setting include_dependencies to packages, changes to its direct or indirect package dependencies will flag the module as changed. This process is repeated until all package dependencies for the module been visited.

sequenceDiagram
  participant GW as go.work
  participant M as Module
  participant P as Package
  participant CML as Changed_Module_List
  participant UML as Unchanged_Module_List
  participant D as Dependency

  GW->>M: Visit Module
  M->>P:Extract all packages for each Module
  P->>M: Returns [module]: [package1,package2]
M->>M: Changes detected?
M->>P: Loop over packages
  P-->>GW: Changes Detected?
  alt Changes Detected
    GW->>CML: Add Module to Changed_Module_List
    M->>D: Has Package Dependency?
    alt Has Dependency
      GW->>CML: Add Dependency to Changed_Module_List
    else No Dependency
      M-->>GW: No Dependency to Add
    end
  else No Changes Detected
    GW->>UML: Add Module to Unchanged_Module_List
    M->>D: Has Dependency in go.work?
    alt Has Dependency
      GW->>UML: Add Dependency to Unchanged_Module_List
    else No Dependency
      M-->>GW: No Dependency to Add
    end
  end
  GW->>GW: Continue Until All Modules Visited

This site is open source. Improve this page.