Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 0 additions & 20 deletions .github/workflows/check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,23 +32,3 @@ jobs:

- name: Verify build for PR
run: ./gradlew check

post_version:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
with:
fetch-tags: true
fetch-depth: 0

- name: Extract version
id: extract_version
run: |
VERSION=$(git describe --tags --dirty)
echo "version=$VERSION" >> $GITHUB_OUTPUT
- name: Posting comment about the build
uses: marocchino/sticky-pull-request-comment@v2
with:
header: version
message: |
The build version for this PR will be: `${{ steps.extract_version.outputs.version }}`
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,9 @@ This library's versioning rules are:
1. If there is a tag related to this commit, the tag will be used as the version name
2. Otherwise, the version name will look like "lastGitTag-numberOfChangesSinceLastTag-shortCommitHash", for example "1.0.0-5-abcd12345". "-dirty" will be appended if the git workspace contains uncommitted changes.

Normally you don't have to worry about versioning as it's fully automatic and determinstic. If changes warrant a new release, then Session devs should push a tag and we'll have a formal release version built.
Normally you don't have to worry about versioning as it's fully automatic and deterministic. If
changes warrant a new release, then Session devs should push a tag,
and we'll have a formal release version built.

#### Development & deployment

Expand Down
Loading