Skip to content

Warning

You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?

Version Forget-Me-Not

Actions
Check and ensure that a Ruby Gem s version has been bumped or updated on a Pull Request
v2.0.1
Star (5)

What it looks like once installation is complete

Version Forget-Me-Not

Forget-me-not flower by Tauno Erik

A Github Action for Ruby projects that checks that the semantic version has been updated in a pull request.

The aim is to remind engineers to update the version before merging, since this step is often forgotten and requires a retroactive fix.

Installation

  1. Create a file called .github/workflows/version-forget-me-not.yml in your Gem's repository with the following YAML (modify as instructed in the comments):

    name: Version Forget-Me-Not
    
    on:
      pull_request:
        branches:
          - main # Change if your default branch is different
        types: [opened, synchronize]
    jobs:
      build:
        runs-on: ubuntu-20.04
    
        steps:
          - uses: simplybusiness/version-forget-me-not@v2
            env:
              ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
              # Change to the file path where you keep the Gem's version.
              # It is usually `lib/<gem name>/version.rb` or in the gemspec file.
              VERSION_FILE_PATH: "<PATH>"
    
  2. Create a new Pull Request to kick off this GitHub Action. You’ll notice it show up at the bottom of your pull request.

    Gem Version status check failing after initial installation

  3. Go to Settings → Branches → Your default branch → Mark Gem Version as required.

    The required status check that needs to be ticked

Version Forget-Me-Not is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

About

Check and ensure that a Ruby Gem s version has been bumped or updated on a Pull Request
v2.0.1

Version Forget-Me-Not is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.