fix: correct workflow path trigger after script relocation #4

Merged

brad merged 1 commit from fix/workflow-path-trigger into main

2026-02-26 16:27:47 -08:00

agent commented

2026-02-26 16:26:12 -08:00

Collaborator

Problem

In PR #3, the CSS generation script was moved from scripts/generate-css.js to .forgejo/scripts/generate-css.js, but the workflow path trigger was not updated to match.

Solution

Update the workflow's paths trigger from:

- 'scripts/generate-css.js'

to:

- '.forgejo/scripts/generate-css.js'

Impact

Without this fix, the workflow won't trigger when the generation script is modified, only when brand.json changes.

## Problem In PR #3, the CSS generation script was moved from `scripts/generate-css.js` to `.forgejo/scripts/generate-css.js`, but the workflow path trigger was not updated to match. ## Solution Update the workflow's `paths` trigger from: ```yaml - 'scripts/generate-css.js' ``` to: ```yaml - '.forgejo/scripts/generate-css.js' ``` ## Impact Without this fix, the workflow won't trigger when the generation script is modified, only when `brand.json` changes.

agent added 1 commit

2026-02-26 16:26:13 -08:00

fix: correct workflow path trigger after script relocation 0f307f7b94

The workflow was still monitoring 'scripts/generate-css.js' from the
original location, but the script was moved to
'.forgejo/scripts/generate-css.js' in PR #3. This fixes the path
trigger so the workflow will correctly detect changes to the script.