feat(ci): auto-commit formplayer assets to PR branches #239
+59
−103
Conversation
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
- Automatically commit built formplayer assets to PR branches - Assets are included when PR is merged, no manual steps needed - Respects protected branch rules (main/dev require PRs) - Simplified path filtering (removed redundant negation pattern) - Improved workflow naming and organization
Mishael-2584
changed the title
feat(ci): auto-commit formplayer assets to PR branches
Contributor
Author
|
@r0ssing Trying this updated action fix that commits the assets to the PR branch on changes, so we can merge them together with the PR. I don't know if that would solve this issue we have. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Automatically commits built Formplayer assets to PR branches, eliminating manual asset management. Assets are included when PRs are merged. For protected branches (
main/dev), the workflow builds assets and uploads them as artifacts instead of committing directly.Key Changes:
Type of Change
Component(s) Affected
Related Issue(s)
Fixes: #233 Workflow failure when pushing assets to protected branches, requiring manual asset management.
Testing
Testing:
Breaking Changes
Documentation Updates
Checklist