[Enhancement] Branch specific Update Type setting

[Warhammer4000]

Context

When there's a merge to a feature branch I want the patch to be updated. When there's a merge to main I want to bump the minor. Similarly I might want to update Major in another branch.

My Current Solution

I detect and set the semver update type in a job and push that info down in the workflow

 - name: Determine semver update type based on branch
        id: determine-semver-update
        run: |
          if [[ ${{ github.ref }} == 'refs/heads/main' ]]; then
            echo "::set-output name=semver-update-type::minor"
          elif [[ ${{ github.ref }} == 'refs/heads/feature' ]]; then
            echo "::set-output name=semver-update-type::patch"
          fi

      - name: Find ProjectSettings.asset & increment its bundleVersion number
        uses: AlexStormwood/UnityAutomatedSemver@v1.1.1
        id: semver-update
        with:
          semver-update-type: ${{ steps.determine-semver-update.outputs.semver-update-type }} 
          project-settings-path: 'ProjectSettings/ProjectSettings.asset'
          should-add-ms-store-trailing-zero: true

Recommendation

- name: Find ProjectSettings.asset & increment its bundleVersion number
        uses: AlexStormwood/UnityAutomatedSemver@v1.1.1
        id: semver-update
        with:
          semver-update-mode: branch #[ options : 'branch','Regular']
          major: 'release' [Required if branch selected]
          minor: 'main' [Required if branch selected]
          patch: 'feature' [Required if branch selected]
          should-add-ms-store-trailing-zero: true

Something like this would be really nice

[AlexStormwood]

Was thinking of this after your last GitHub issue post where you showed your workflow, too!

I think adding semver update modes is the right idea, and the way you're updating semver numbers depending on the branch merged into is new to me - the code you've shown is a huge help but it might take some time to put into place.

I'm gonna implement this alongside another update mode: conventional commits. With all the NodeJS work I've been doing lately, "automated semver" over there means "write good commits and never worry about semver again", so I'd like to bring some of that to here.

That'll be a mode so it won't be forced on anyone, but it means I need to refactor things a bit to make multiple mode options work better.

[AlexStormwood]

Haven't implemented this yet - I was stumped on how to do this in a more-effective way than just getting the branch name as an input, which wouldn't have been an improvement over how you're currently handling this.

But, just as a note for myself - I think I've figured it out:

const { exec } = require('child_process');
exec('git branch --show-current', (err, stdout, stderr) => {
    if (stderr) {
        
	console.log("Error!");
    }

	console.log(stdout.trim());
});

That stdout.trim() is the name of the current branch. Gotta make sure that GitHub Actions runners actually treats the checked-out repo as the current repo so that git branch --show-current would work, but if that works: I can just add extra inputs for "bumpXyzOnBranch" and that'd do it.

I just released a v2 of this action so I'm gonna give that time to simmer and let people adjust to that, but this will be the next update. Shouldn't even break anything since it'd just be a matter of adding more inputs and conditional code, but I wanna make sure I'm not blitzing through changes without having some time to adjust to the latest big changes.

[Warhammer4000]

I just checked the update. Brother you have done an overkill with the project. It seems you need some information on PS4 versioning documentation. I'll see if I can find it somehow. No promises though. Currently stumped with other issues on our game. For now, will be sticking to the last version. But will be testing out the v2 soon on other projects.