[CHORE]: Tighten up the actions, script to be more robust/self contained #29

Closed
opened 2026-04-15 03:42:12 +00:00 by imAsparky · 0 comments
Owner

What needs to be done?

action.yaml — takes on all git responsibility
New inputs needed:

git-user-email (default: action@forgejo.com)
git-user-name (default: git-herald)

New output needed:

commit-sha — the new SHA after push, so the caller can stamp PR statuses

New steps to add after the script runs:

git restore --source origin/main -- CHANGELOG.md (currently lives in the caller — belongs here)
git checkout $GITHUB_HEAD_REF (same)
git status --porcelain guard
git config, git add, git commit with [skip ci]
Configure remote URL with token, then git push

Scope

Refactoring

Definition of Done

  • merge into main

Additional Context

No response

### What needs to be done? action.yaml — takes on all git responsibility New inputs needed: git-user-email (default: action@forgejo.com) git-user-name (default: git-herald) New output needed: commit-sha — the new SHA after push, so the caller can stamp PR statuses New steps to add after the script runs: git restore --source origin/main -- CHANGELOG.md (currently lives in the caller — belongs here) git checkout $GITHUB_HEAD_REF (same) git status --porcelain guard git config, git add, git commit with [skip ci] Configure remote URL with token, then git push ### Scope Refactoring ### Definition of Done - [ ] merge into main ### Additional Context _No response_
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dunwright/git-herald#29
No description provided.