Move to GitFlow strategy [ci patch inc]

[HyperWinX]

Update workflows to comply with GitFlow strategy rules.

[mentatbot]

I'm getting to work. See my steps and track my cost here.

• Wake on any new activity.
  _{I always see new activity while actively working. When paused, I'll only respond when tagged unless this box is checked.}

[mentatbot]

Hi there! I've reviewed your PR for migrating to GitFlow and found a few issues that should be addressed:

1. Duplicate versioning jobs

The same versioning jobs appear in both testing.yml and version-increment.yml. This could lead to duplicate version increments if both workflows run for the same change.

2. Inconsistent dependencies

• In testing.yml, the versioning-minor-increment job depends on testing (needs: [testing]), but versioning-patch-increment doesn't have this dependency
• In version-increment.yml, neither versioning job depends on testing

This means versions could be incremented without tests passing in some cases.

3. Incorrect commit messages

Both versioning-minor-increment jobs use the commit message "Increment patch version" even though they're incrementing the minor version.

Recommendations:

1. Separate concerns clearly:

   • testing.yml should only handle testing on PRs
   • version-increment.yml should handle version increments on merged PRs

2. Fix dependency structure:

   • All version increment jobs should depend on tests passing
   • Consider adding needs: [testing] to the patch increment job in testing.yml

3. Fix commit messages:

   • Change the commit message in minor increment jobs to say "Increment minor version"

4. Clarify workflow purpose:

   • Consider adding comments explaining when each workflow runs in GitFlow
   • Document which branch tests run on and when versions get incremented

Would you like me to help with implementing these changes?