Skip to content

release-vfsforgit: fix heredoc and add workflow_dispatch trigger#884

Merged
dscho merged 2 commits intovfs-2.53.0from
fix-release-vfsforgit
Apr 17, 2026
Merged

release-vfsforgit: fix heredoc and add workflow_dispatch trigger#884
dscho merged 2 commits intovfs-2.53.0from
fix-release-vfsforgit

Conversation

@dscho
Copy link
Copy Markdown
Member

@dscho dscho commented Apr 17, 2026

This fixes the failure in https://github.com/microsoft/git/actions/runs/24558034660/job/71799344023 and adds a workflow_dispatch trigger so the workflow can be re-run manually without creating a new release.

Commit 1: Replace the broken heredoc (cat <<EOF) with a simple quoted string. The heredoc failed because the YAML run: | block preserves indentation, so the closing EOF delimiter was never at column 0.

Commit 2: Add workflow_dispatch with a tag input (same pattern as the winget workflow), and consolidate the tag into a single TAG_NAME env var set at workflow level.

dscho added 2 commits April 17, 2026 12:16
The heredoc used to construct PR_BODY fails in GitHub Actions because
the YAML `run: |` block preserves its indentation when passing the
script to bash. The closing `EOF` delimiter ends up indented with
spaces, but bash's `<<EOF` requires it at column 0 (only `<<-EOF`
strips leading whitespace, and only tabs at that). This caused
https://github.com/microsoft/git/actions/runs/24558034660/job/71799344023
to fail with "here-document at line 38 delimited by end-of-file
(wanted `EOF')".

Replace the heredoc with a simple double-quoted string assignment,
which works correctly regardless of indentation context.

Assisted-by: Claude Opus 4.6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add a workflow_dispatch trigger so the workflow can be re-run manually
when the release-triggered run fails (as happened in
https://github.com/microsoft/git/actions/runs/24558034660/job/71799344023).
Without this, the only way to retry is to create a new release.

This follows the same pattern as the winget workflow, which already
has a workflow_dispatch trigger with a `tag` input. The tag is
resolved once in a top-level `env:` block via
`${{ github.event.inputs.tag || github.event.release.tag_name }}`
so both trigger paths feed the same `TAG_NAME` environment variable.
The old `Compute tag name` step and the local `TAG` shell variable
are no longer needed.

Assisted-by: Claude Opus 4.6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho
Copy link
Copy Markdown
Member Author

dscho commented Apr 17, 2026

Tested successfully: the workflow run completed and created microsoft/VFSForGit#1948.

@dscho dscho force-pushed the fix-release-vfsforgit branch from fb5e2b9 to aa5b514 Compare April 17, 2026 11:01
@dscho dscho marked this pull request as ready for review April 17, 2026 11:04
@dscho dscho merged commit 5990fbb into vfs-2.53.0 Apr 17, 2026
289 of 336 checks passed
@dscho dscho deleted the fix-release-vfsforgit branch April 17, 2026 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants