Implemented support for the AddonCompartmentFrame
.
#58
Workflow file for this run
This file contains 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
name: Package and release | |
# we need to let GitHub know _when_ we want to release, typically only when we create a new tag. | |
# this will target only tags, and not all pushes to the master branch. | |
# this part can be heavily customized to your liking, like targeting only tags that match a certain word, | |
# other branches or even pullrequests. | |
on: | |
push: | |
tags: | |
- '**' | |
# a workflow is built up as jobs, and within these jobs are steps | |
jobs: | |
# "release" is a job, you can name it anything you want | |
release: | |
# we can run our steps on pretty much anything, but the "ubuntu-latest" image is a safe bet | |
runs-on: ubuntu-latest | |
env: | |
GITHUB_OAUTH: ${{ secrets.GITHUB_TOKEN }} # "GITHUB_TOKEN" is a secret always provided to the workflow | |
# for your own token, the name cannot start with "GITHUB_" | |
# "steps" holds a list of all the steps needed to package and release our AddOn | |
steps: | |
# we first have to clone the AddOn project, this is a required step | |
- name: Clone project | |
uses: actions/checkout@v3 | |
with: | |
fetch-depth: 0 # gets git history for changelogs | |
# once cloned, we just run the GitHub Action for the packager project | |
- name: Package and release | |
uses: BigWigsMods/packager@v2.0.8 |