This repository has been archived by the owner on Oct 10, 2024. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
auto release on semver-named tags (#190)
* auto release zip'd builds * merged build steps into the Release and Debug jobs * zips up builds using win10's tar.exe * publishes the zip files using github's release api, allowing anyone to download them even without a github account * kept artifacts just to avoid breaking the discord webhook. could change this at some point. * bugfix: strings are single-quoted * don't actually know. seems like yaml supports either. * bugfix: removed '.' directory from zip archive * auto-release now triggers on semver-named tags steps to trigger auto-release: 1. push your commit to any branch 2. tag your commit using semver name (see below) 3. push tag for semver naming, please use this format: v1.2.3-featureName+1.0.1 v1.2.3 refers to the main branch version when you create your feature branch (or last pulled from main) +1.0.1 refers to the version of your feature, independent of the main branch version. the values "1.2.3" and "1.0.1": * the last number represents a minor change (bugfix, regenerating cpp scaffolding, changing a literal, etc) * the middle number represents a new feature (so, when merging feature branches into main, tag that and increment this middle number) * the first number represents a major rewrite of the entire project. incrementing a number should 'reset' the numbers to the right. eg; v1.0.23 should become v1.1.0 once merging a new feature. any individual number can extend beyond single digits, ex: v1.0.10 is the tenth minor patch. * bugfix: release already exists merged debug job into one giant BuildAndRelease job. * test feature 112 commit name doesn't affect anything, it's just for my reference. testing the generation of the changelog by auto-release for semver-named feature branches. * test feature 113 no-release commit name doesn't affect anything, it's just for my reference. testing the generation of the changelog by auto-release for semver-named feature branches. * test feature 114 no-release commit name doesn't affect anything, it's just for my reference. testing the generation of the changelog by auto-release for semver-named feature branches. * test feature 115 commit name doesn't affect anything, it's just for my reference. testing the generation of the changelog by auto-release for semver-named feature branches. * test main 101 commit name doesn't affect anything, it's just for my reference. testing the generation of the changelog by auto-release * discord webhook should link to the release now seems a little janky but it works on my private repo & discord, i swear. artifacts are still kept for bitbot compatibility * separated jobs * bugfix: error in yaml syntax * bugfix: more indentation issues * bugfix: more indentation.. * standardized line endings and indentations line by line the entire file. if this fails then github actions is broken. * bugfix: forgot checkout action
- Loading branch information