Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

automation of Git tags and GitHub Releases for each release version (submitted to Unity Asset Store) #131

Open
cvan opened this issue Feb 13, 2018 · 3 comments
Labels
ARCHIVED CLOSED at time of archiving meta

Comments

@cvan
Copy link
Contributor

cvan commented Feb 13, 2018

I can provide a Node or shell build script (there are a few decent npm packages that do this too; I'll have to check my list and test them again).

@cvan cvan added the meta label Feb 13, 2018
@cvan cvan added this to the Polished community release milestone Feb 13, 2018
@cvan
Copy link
Contributor Author

cvan commented Feb 13, 2018

@delapuente: looks like you've done this for both versions (thanks!)

which comands are you using? just manually building the project in Unity to Build/ and then git commit -am 'Version X.Y.Z' && git tag && git push --tags?

@delapuente
Copy link
Contributor

I export the demo to /Build, then export the package, commit to master and tag.

@cvan cvan changed the title create Git tags and GitHub Releases for each release version (submitted to Unity Asset Store) automation of Git tags and GitHub Releases for each release version (submitted to Unity Asset Store) Feb 13, 2018
@cvan cvan removed this from the Polished community release milestone Feb 13, 2018
@cvan
Copy link
Contributor Author

cvan commented Mar 21, 2018

Roughly these steps (correct me if I'm wrong, @salva):

git checkout master --force
git pull --rebase
# manually build Unity project (there are some CLIs that do this; I'd need to test them before I recommend it)
#
# wait for `Build/` to be done
export unity_version='1.X.X'
git tag $unity_version && git push && git push --tags

@cknowles-admin cknowles-admin added the ARCHIVED CLOSED at time of archiving label Jul 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ARCHIVED CLOSED at time of archiving meta
Projects
None yet
Development

No branches or pull requests

3 participants