A couple questions concerning GitHub Actions

[rfalanga]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

General

Discussion Details

At work I've convinced them that we should be using GitHub Releases. We're going to try to do something I don't know if it is possible to do. There's a lot I could bring up, but I'll restrict myself to 2 questions.

First, during a GitHub Action, which would be running on a self-hosted runner (I don't know if that is pertinent, but I'll mention it anyway) we'd like to get the body of the PR to be able to insert that into the body of a GitHub Release. Is that possible? If so, how is that done?

Second, when I've created git tags, and that occasional GitHub Release, I've always used semantic versioning. Is there any way to determine what is the maximum semantic version, so we can programmatically come up with the next semantic version number? If so, how is that done?

[SIMARSINGHRAYAT]

your decision is great i think ts better to use github at workspace for more productivity, you can refer github documents to support your case.

[SIMARSINGHRAYAT]

For both of your GitHub Actions questions:

Question 1: Getting PR body in a self-hosted action and inserting into a Release

Use the github.event.pull_request.body context variable to access the PR body:

- name: Create Release with PR body
  uses: softprops/action-gh-release@v1
  with:
    body: ${{ github.event.pull_request.body }}

For self-hosted runners, ensure you're using the pull_request trigger and the PR context will be available.

Question 2: Determining maximum semantic version and calculating next version

Parse existing git tags and increment programmatically:

- name: Get next version
  run: |
    LATEST_TAG=$(git describe --tags --sort=-version:refname --abbrev=0 2>/dev/null || echo "v0.0.0")
    LATEST_VERSION=${LATEST_TAG#v}
    IFS='.' read -r MAJOR MINOR PATCH <<< "$LATEST_VERSION"
    NEXT_VERSION="v$MAJOR.$MINOR.$((PATCH + 1))"
    echo "NEXT_VERSION=$NEXT_VERSION" >> $GITHUB_ENV

Alternatively, use action like actions/github-script or npm packages like semver for more robust version handling. Many projects use conventional-commits to automatically determine version bumps (major/minor/patch) based on commit messages.

[Rod-at-DOH]

Is that second code Bash?