Skip to content

Accept exact source SHA for Pages deployments - #2

Closed
LittleLittleCloud wants to merge 1 commit into
mainfrom
littlelittlecloud-accept-source-sha-dispatch
Closed

LittleLittleCloud wants to merge 1 commit into
mainfrom
littlelittlecloud-accept-source-sha-dispatch

Conversation

@LittleLittleCloud

Copy link
Copy Markdown
Member

Summary

  • add an optional source_sha workflow-dispatch input for an exact RazorConsole/RazorConsole commit
  • validate supplied values as exactly 40 hexadecimal characters before checkout
  • build the requested SHA for manual dispatches and source main for push, schedule, PR, and input-less manual runs
  • document exact-SHA manual recovery and cross-repository API dispatch

Validation

  • actionlint v1.7.12
  • PyYAML parse of .github/workflows/pages.yml
  • SHA contract checks for valid and malformed values
  • git diff --check

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@LittleLittleCloud

Copy link
Copy Markdown
Member Author

Superseded by the decision to build and deploy production directly from RazorConsole/RazorConsole to the custom domain razorconsole.com; cross-repository exact-SHA dispatch is no longer needed.

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.

1 participant