Tracks the current build count with a .build-number file.
Add this line to your application's Gemfile:
gem 'build_integer'
And then execute:
$ bundle
Or install it yourself as:
$ gem install build_integer
# start
BuildInteger.find # finds or creates a .build-number file and returns the current build number
# > 10
BuildInteger.increment # increases the number by 1
# > 11
BuildInteger.decrement # decreases the number by 1
# > 10
BuildInteger.set 5 # set the build number to 5
# > 5
BuildInteger.current # returns the current build number
# > 5
BuildInteger.reset # sets the build number to 10
# > 0
After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.
The gem is available as open source under the terms of the MIT License.
FAQs
Unknown package
We found that build_integer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.