In addition to driving animation, the Skeleton asset is responsible for:Īnimation Retargeting - which allows the adjustment of animations for characters with different proportions.Ĭreating and saving Sockets - which allows you to attach things to your characters. The sharing of a Skeleton asset between Skeletal Meshes provides a way for you to share animations between characters or even entire Animation Blueprints used to define animation logic for a character. Additionally, workspace_dispatch can only be run from GitHub.The primary focus of the Skeleton asset is to handle animation data, not the Skeletal Mesh.Īnother important facet of the Skeleton asset is that if your Skeletal Meshes share the same Skeleton asset (pending some basic rules are met), you can share animation data even if the hierarchy does not exactly match. Worth noticing is that none of the GitHub environmental variables will be available and you will have to somewhat recreate those. Any change applied to the file can be tested by re-running act. To run the action locally, open your terminal and cd to the location of this file, then simply run act.Īct will run the built-in workflow which is set to point to the entrypoint.sh file at this location. By using act, it can be entirely run locally, without the need of pushing to GitHub. This action comes with a built-in workflow that helps with development.
version (default: latest): The Grav version to utilize for building the Skeleton package.This action comes with a set of useful input parameters that can be used for customizing the build. All the existing packages from that version will get now overwritten and will contain the latest version of Grav and the Skeleton dependencies.
Docs2 skeleton update#
The Manual mode, instead, can be reached in GitHub under Actions -> Build Skeleton -> Run workflow, where you will have to specify the release tag version you are targeting to rebuilt.Īssuming your latest Skeleton release is v1.0.0 but a new version of Grav was released and you want to update your packages, you would run the Manual workflow and type v1.0.0 as target tag. Once a new Release is created, the workflow will spin off. To use the automatic mode, you don't have to do anything other than follow the standard procedure of GitHub release. Manually: if you don't have anything to release but you want to rebuild the packages to use the latest version of Grav or any of your Skeleton dependencies, you can use this way.Automatically: every time a new release of your skeleton is published on GitHub, the workflow will run, generate the packages and upload them on your just published release.The workflow in combination with this action supports the creation of Skeleton packages in two ways: You are now ready to build your skeleton. uses: name: Extract Tag run: echo "SKELETON_VERSION=$ file: dist/*.zip overwrite: true file_glob: true Description: 'Target tag for re-upload ' required: true default: ' ' version:ĭescription: 'Which Grav release to use ' required: true default: 'latest ' admin:ĭescription: 'Create also a package with Admin ' required: true default: true jobs:
0 kommentar(er)
