chore: make deploy workflow generic using GitHub Actions context#4
Open
itinsecurity wants to merge 1 commit into
Open
chore: make deploy workflow generic using GitHub Actions context#4itinsecurity wants to merge 1 commit into
itinsecurity wants to merge 1 commit into
Conversation
Replace hardcoded bjornarfl/FlowState-TM references with GitHub Actions context expressions so the workflow works for any fork without manual edits. - VITE_BASE_PATH and VITE_REPO_URL now derived from github.repository - DEPLOY_REMOTE built from github.repository so package.json has no owner reference - Remove unused homepage field from package.json Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bjornarfl/FlowState-TMreferences in the deploy workflow with GitHub Actions context expressions, so the workflow works for any fork without manual editsVITE_BASE_PATHandVITE_REPO_URLare now derived fromgithub.repositoryDEPLOY_REMOTEis built fromgithub.repository, removing the need for a hardcoded owner/repo inpackage.jsonhomepagefield frompackage.jsonMotivation
Forks currently have to manually edit
deploy.ymlandpackage.jsonbefore their GitHub Pages deploy works. These changes make the workflow self-configuring based on the repository it runs in.Test plan
bjornarfl/FlowState-TMafter merge🤖 Generated with Claude Code