🚀 Here's the PR! #4

💎 Sweep Pro: You have unlimited Sweep issues

Actions

[ ] ↻ Restart Sweep
Step 1: 🔎 Searching

Here are the code search results. I'm now analyzing these search results to write the PR.

Relevant files (click to expand). Mentioned files will always appear here.

https://github.com/saturdaymp/Migrator/blob/6b086d90385ac5012dfc8c90a6e3e343cde6d0c0/README.md#L1-L34 https://github.com/saturdaymp/Migrator/blob/6b086d90385ac5012dfc8c90a6e3e343cde6d0c0/README.md#L1-L34

Step 2: ⌨️ Coding

`.github/workflows/gitversion.yml`

First, create a new directory named `.github` in the repository root. Then, inside the `.github` directory, create a new directory named `workflows`. Finally, create a new file named `gitversion.yml` inside the `.github/workflows` directory with the following contents:

name: GitVersion

on:
  push:
    branches:
      - main

jobs:
  gitversion:
    name: Determine Version
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v3
      with:
        fetch-depth: 0

    - name: Install GitVersion
      uses: gittools/actions/gitversion/setup@v0.9.15
      with:
        versionSpec: '5.x'

    - name: Determine Version
      id: gitversion
      uses: gittools/actions/gitversion/execute@v0.9.15
      with:
        useConfigFile: true
        configFilePath: GitVersion.yml

    - name: Output Version
      run: |
        echo "SemVer: ${{ steps.gitversion.outputs.semVer }}"
        echo "MajorMinorPatch: ${{ steps.gitversion.outputs.majorMinorPatch }}"

`GitVersion.yml`

1. This file will configure GitVersion to use trunk-based development with release branches. The main branch will be treated as the mainline, with release branches following the format release-*. Builds from the main branch will be flagged as "ci" builds. 2. mode: Mainline branches: main: regex: ^main$ tag: '' increment: Patch prevent-increment-of-merged-branch-version: true track-merge-target: false is-release-branch: false is-mainline: true pre-release-weight: 55000 release: regex: ^releases?[/-] tag: beta increment: Patch prevent-increment-of-merged-branch-version: true track-merge-target: false is-release-branch: true pre-release-weight: 30000 feature: regex: ^features?[/-] tag: alpha increment: Inherit prevent-increment-of-merged-branch-version: false track-merge-target: false is-release-branch: false pull-request: regex: ^(pull|pull\-requests|pr)[/-] tag: PR increment: Inherit prevent-increment-of-merged-branch-version: false tag-number-pattern: '[/-](?\d+)[-/]' track-merge-target: false is-release-branch: false ignore: sha: [] merge-message-formats: {}

`README.md`

1.

--- 
+++ 
@@ -1,3 +1,13 @@
+## Versioning
+
+Migrator uses [GitVersion](https://gitversion.net/) to automatically generate version numbers based on the state of the Git repository. The versioning scheme follows trunk-based development with release branches:
+
+- The `main` branch contains the latest development version and will produce versions like `1.2.3-ci.1`
+- Release branches (`release-*`) contain stable versions and will produce versions like `1.2.3-beta.1`
+- Tags are used to mark specific releases
+
+The GitVersion configuration can be found in [GitVersion.yml](GitVersion.yml).
+
 ## Contribute

 There are several ways you help can make Migrator better:

Step 3: 🔄️ Validating

Your changes have been successfully made to the branch sweep/add_a_github_action_that_calculates_the. I have validated these changes using a syntax checker and a linter.

[!TIP] To recreate the pull request, edit the issue title or description.

This is an automated message generated by Sweep AI.

saturdaymp / Migrator

Sweep: Add a GitHub action that calculates the next version number using GitVersion #3