Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# description of this workflow, can be anything you want
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

# specify the environment variables used by the packager, matching the secrets from the project on GitHub
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@v2
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

# another example where we supply additional arguments, this example is specifically to release
# for the Burning Crusade Classic version of the game and doesn't upload to WoWInterface
- name: Package and release for Burning Crusade Classic
uses: BigWigsMods/packager@v2
with:
args: -g bcc -w 0
Loading