Welcome to omniauth-workable gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file lib/omniauth/workable. To experiment with that code, run bin/console for an interactive prompt.
Add this line to your application's Gemfile:
gem 'omniauth-workable'
And then execute:
$ bundle install
Or install it yourself as:
$ gem install omniauth-workable
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.
This repository leverages Google Cloud's release-please-action for releasing new version for the code. Please ensure your commits follow the Convetional Commits convention. Otherwise, the merge request won't be release.
Bug reports and pull requests are welcome on GitHub at https://github.com/screenloop/omniauth-workable.
FAQs
Unknown package
We found that omniauth-workable 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.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.