omniauth-identity 3.1.4 → 3.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
data/CONTRIBUTING.md CHANGED
@@ -1,144 +1,168 @@
1
1
  # Contributing
2
2
 
3
- Bug reports and pull requests are welcome on GitHub at [https://github.com/omniauth/omniauth-identity][🚎src-main].
3
+ Bug reports and pull requests are welcome on [CodeBerg][📜src-cb], [GitLab][📜src-gl], or [GitHub][📜src-gh].
4
4
  This project should be a safe, welcoming space for collaboration, so contributors agree to adhere to
5
5
  the [code of conduct][🤝conduct].
6
6
 
7
7
  To submit a patch, please fork the project, create a patch with tests, and send a pull request.
8
8
 
9
- Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog].
9
+ Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog] if you make changes.
10
+
11
+ ## Developer Certificate of Origin
12
+
13
+ In order to protect users of this project, we require all contributors to comply with the
14
+ [Developer Certificate of Origin](https://developercertificate.org/).
15
+ This ensures that all contributions are properly licensed and attributed.
10
16
 
11
17
  ## Help out!
12
18
 
13
- Take a look at the `reek` list which is the file called `REEK` and find something to improve.
19
+ Take a look at the open issues and pull requests, or use the gem and find something to improve.
14
20
 
15
21
  Follow these instructions:
16
22
 
17
- 1. Fork the repository
18
- 2. Create a feature branch (`git checkout -b my-new-feature`)
19
- 3. Make some fixes.
20
- 4. Commit changes (`git commit -am 'Added some feature'`)
21
- 5. Push to the branch (`git push origin my-new-feature`)
22
- 6. Make sure to add tests for it. This is important, so it doesn't break in a future release.
23
- 7. Create new Pull Request.
24
-
25
- ## Appraisals
23
+ 1. Join the Discord: [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
24
+ 2. Fork the repository
25
+ 3. Create your feature branch (`git checkout -b my-new-feature`)
26
+ 4. Make some fixes.
27
+ 5. Commit your changes (`git commit -am 'Added some feature'`)
28
+ 6. Push to the branch (`git push origin my-new-feature`)
29
+ 7. Make sure to add tests for it. This is important, so it doesn't break in a future release.
30
+ 8. Create new Pull Request.
31
+ 9. Announce it in the channel for this org in the [Discord][✉️discord-invite]!
32
+
33
+ ## Executables vs Rake tasks
34
+
35
+ Executables shipped by dependencies, such as kettle-dev, and stone_checksums, are available
36
+ after running `bin/setup`. These include:
37
+
38
+ - gem_checksums
39
+ - kettle-changelog
40
+ - kettle-commit-msg
41
+ - kettle-dev-setup
42
+ - kettle-dvcs
43
+ - kettle-pre-release
44
+ - kettle-readme-backers
45
+ - kettle-release
46
+
47
+ There are many Rake tasks available as well. You can see them by running:
48
+
49
+ ```shell
50
+ bin/rake -T
51
+ ```
26
52
 
27
- From time to time the appraisal gemfiles in `gemfiles/` will need to be updated.
53
+ ## Code quality checks
28
54
 
29
- Create or update them with the commands:
55
+ Run the Reek task when you want a smell check that fails on current findings:
30
56
 
31
- ```console
32
- BUNDLE_GEMFILE=Appraisal.root.gemfile bundle
33
- BUNDLE_GEMFILE=Appraisal.root.gemfile bundle exec appraisal update
34
- bundle exec rake rubocop_gradual:autocorrect
57
+ ```shell
58
+ bin/rake reek
35
59
  ```
36
60
 
37
- NOTE: Commands need to be run from the devcontainer if old Rails or old sqlite3 won't install for you locally.
61
+ Refresh the checked-in `REEK` backlog through the rake task, not by redirecting
62
+ the raw `reek` executable output. The rake task uses the project bundle and
63
+ avoids stale generated binstubs shadowing the Reek gem executable:
38
64
 
39
- When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
40
-
41
- ### We commit, and don't commit, our "gemfile.lock" files
65
+ ```shell
66
+ bin/rake reek:update
67
+ ```
42
68
 
43
- Thanks to [Appraisal2](https://github.com/appraisal-rb/appraisal2) we have a `gemfiles/*.gemfile` suite
44
- in addition to the main `Gemfile` at the root of the project.
45
- We run a workflow against the main Gemfile, which has a `Gemfile.lock` committed, and
46
- we also run workflows against each of the Appraisal2 `gemfiles/*.gemfile` suite,
47
- which **do not** have `gemfiles/*.gemfile.lock` committed.
69
+ ## Environment Variables for Local Development
70
+
71
+ Below are the primary environment variables recognized by stone_checksums (and its integrated tools). Unless otherwise noted, set boolean values to the string "true" to enable.
72
+
73
+ General/runtime
74
+ - DEBUG: Enable extra internal logging for this library (default: false)
75
+ - REQUIRE_BENCH: Enable `require_bench` to profile requires (default: false)
76
+ - CI: When set to true, adjusts default rake tasks toward CI behavior
77
+
78
+ Coverage (kettle-soup-cover / SimpleCov)
79
+ - K_SOUP_COV_DO: Enable coverage collection (default: true in `mise.toml`)
80
+ - K_SOUP_COV_FORMATTERS: Comma-separated list of formatters (html, xml, rcov, lcov, json, tty)
81
+ - K_SOUP_COV_MIN_LINE: Minimum line coverage threshold (integer, e.g., 100)
82
+ - K_SOUP_COV_MIN_BRANCH: Minimum branch coverage threshold (integer, e.g., 100)
83
+ - K_SOUP_COV_MIN_HARD: Fail the run if thresholds are not met (true/false)
84
+ - K_SOUP_COV_MULTI_FORMATTERS: Enable multiple formatters at once (true/false)
85
+ - K_SOUP_COV_OPEN_BIN: Path to browser opener for HTML (empty disables auto-open)
86
+ - MAX_ROWS: Limit console output rows for simplecov-console (e.g., 1)
87
+ Tip: When running a single spec file locally, you may want `K_SOUP_COV_MIN_HARD=false` to avoid failing thresholds for a partial run.
88
+
89
+ GitHub API and CI helpers
90
+ - GITHUB_TOKEN or GH_TOKEN: Token used by `ci:act` and release workflow checks to query GitHub Actions status at higher rate limits
91
+
92
+ Releasing and signing
93
+ - SKIP_GEM_SIGNING: If set, skip gem signing during build/release
94
+ - GEM_CERT_USER: Username for selecting your public cert in `certs/<USER>.pem` (defaults to $USER)
95
+ - SOURCE_DATE_EPOCH: Reproducible build timestamp.
96
+ - `kettle-release` will set this automatically for the session.
97
+ - Not needed on bundler >= 2.7.0, as reproducible builds have become the default.
98
+
99
+ Git hooks and commit message helpers (exe/kettle-commit-msg)
100
+ - GIT_HOOK_BRANCH_VALIDATE: Branch name validation mode (e.g., `jira`) or `false` to disable
101
+ - GIT_HOOK_FOOTER_APPEND: Append a footer to commit messages when goalie allows (true/false)
102
+ - GIT_HOOK_FOOTER_SENTINEL: Required when footer append is enabled — a unique first-line sentinel to prevent duplicates
103
+ - GIT_HOOK_FOOTER_APPEND_DEBUG: Extra debug output in the footer template (true/false)
104
+
105
+ Git diff driver setup
106
+ - Local setup writes repository `.gitattributes` entries and local Git `diff.smorg-*` command config so this checkout uses StructuredMerge semantic diffs.
107
+ - Global setup registers `diff.smorg-*` commands once in the user Git config; use it when you work across several StructuredMerge-enabled repositories.
108
+ - Include-file setup writes `.git/smorg/config` and includes it from local Git config, keeping command registrations out of the repository files.
109
+ - Git hosting forges generally ignore external diff drivers, so pull request views may still show raw textual diffs even when local `git diff` uses semantic drivers.
48
110
 
49
- ```
50
- # Lock/Unlock Deps Pattern
51
- #
52
- # Two often conflicting goals resolved!
53
- #
54
- # - deps_unlocked.yml
55
- # - All runtime & dev dependencies, but does not have a `gemfiles/*.gemfile.lock` committed
56
- # - Uses an Appraisal2 "deps_unlocked" gemfile, and the current MRI Ruby release
57
- # - Know when new dependency releases will break local dev with unlocked dependencies
58
- # - Broken workflow indicates that new releases of dependencies may not work
59
- #
60
- # - deps_locked.yml
61
- # - All runtime & dev dependencies, and has a `Gemfile.lock` committed
62
- # - Uses the project's main Gemfile, and the current MRI Ruby release
63
- # - Matches what contributors and maintainers use locally for development
64
- # - Broken workflow indicates that a new contributor will have a bad time
65
- #
111
+ ```console
112
+ K_JEM_TEMPLATING=true bundle exec kettle-jem install
66
113
  ```
67
114
 
68
- ## The Reek List
115
+ Troubleshooting Git diffs
116
+ - Use `git diff --no-ext-diff` to compare against Git's built-in diff output.
117
+ - Use `git diff --no-textconv` when a textconv projection obscures the raw file bytes you need to inspect.
118
+ - If Git reports a missing `smorg-*` executable, rerun `bundle install` and the setup command above, then check `git config --local --get-regexp '^diff\.smorg-'`.
119
+ - To remove managed local entries, run `K_JEM_TEMPLATING=true bundle exec kettle-jem install --undo`; remove global command registrations with `git config --global --unset-all diff.smorg-ruby.command`.
69
120
 
70
- Take a look at the `reek` list which is the file called `REEK` and find something to improve.
121
+ For a quick starting point, this repository’s `mise.toml` defines the shared defaults, and `.env.local` can override them locally. Copy `.env.local.example` to `.env.local`, use `KEY=value` lines, and either activate `mise` in your shell or run commands through `mise exec -C /path/to/project -- ...`.
71
122
 
72
- To refresh the `reek` list:
123
+ ## Appraisals
73
124
 
74
- ```console
75
- bundle exec reek > REEK
76
- ```
125
+ From time to time the [appraisal2][🚎appraisal2] gemfiles in `gemfiles/` will need to be updated.
126
+ Generated appraisal and CI workflow floors are controlled by `ruby.test_minimum`
127
+ in `.structuredmerge/kettle-jem.yml`; this project was templated with `ruby.test_minimum: 2.4`.
128
+ That value describes the lowest Ruby version expected to run the test/development
129
+ toolchain, and it may be higher than the gemspec runtime floor.
77
130
 
78
- ## Run Tests
131
+ They are created and updated with the commands:
79
132
 
80
- NOTE: To run *all* tests have the following databases installed, configured, and running.
81
-
82
- 1. [RethinkDB](https://rethinkdb.com), an open source, real-time, web database, [installed](https://rethinkdb.com/docs/install/) and [running](https://rethinkdb.com/docs/start-a-server/), e.g.
83
- ```console
84
- brew install rethinkdb
85
- rethinkdb
86
- ```
87
- 2. [MongoDB](https://docs.mongodb.com/manual/administration/install-community/)
88
- ```console
89
- brew tap mongodb/brew
90
- brew install mongodb-community@4.4
91
- mongod --config /usr/local/etc/mongod.conf
92
- ```
93
- 3. [CouchDB](https://couchdb.apache.org) - download the .app, or:
94
- ```console
95
- brew install couchdb
96
- ```
97
- CouchDB 3.x requires a set admin password set before startup.
98
- Add one to your `$HOMEBREW_PREFIX/etc/local.ini` before starting CouchDB e.g.:
99
- ```ini
100
- [admins]
101
- admin = yourabsolutesecret
102
- ```
103
- Also add whatever password you set to your `.env.local`:
104
- ```dotenv
105
- export COUCHDB_PASSWORD=yourabsolutesecret
106
- ```
107
- Then start the CouchDB service
108
- ```console
109
- brew services start couchdb
110
- ```
111
-
112
- Now you can run any of the tests!
113
-
114
- To run all tests on all databases (except RethinkDB):
115
133
  ```console
116
- bundle exec rake spec:orm:all
134
+ bin/rake appraisal:update
117
135
  ```
118
136
 
119
- To run all tests that do not require any additional services, i.e. excluding MongoDB, CouchDB, & RethinkDB:
137
+ If you need to reset all gemfiles/*.gemfile.lock files:
138
+
120
139
  ```console
121
- bundle exec rake test
140
+ bin/rake appraisal:reset
122
141
  ```
123
142
 
124
- To run a specific DB:
125
- ```console
126
- # CouchDB / CouchPotato
127
- bundle exec rspec spec spec_orms --tag 'couchdb'
143
+ When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
128
144
 
129
- # ActiveRecord and Sequel, as they both use the in-memory SQLite driver.
130
- bundle exec rspec spec spec_orms --tag 'sqlite3'
145
+ ## Run Tests
131
146
 
132
- # NOTE - mongoid and nobrainer specs can't be isolated with "tag" because it still loads everything,
133
- # and the two libraries are fundamentally incompatible.
147
+ Run tests via `kettle-test` (provided by `kettle-test`). It runs RSpec, writes the full log to
148
+ `tmp/kettle-test/rspec-TIMESTAMP.log`, and prints a compact highlight block with timing, seed,
149
+ pass/fail count, failing example list, and SimpleCov coverage percentages.
134
150
 
135
- # MongoDB / Mongoid
136
- bundle exec rspec spec_orms/mongoid_spec.rb
151
+ ```console
152
+ bundle exec kettle-test
153
+ ```
137
154
 
138
- # RethinkDB / NoBrainer (Ignored by CI! see spec file for reasons)
139
- bundle exec rspec spec_ignored/nobrainer_spec.rb
155
+ For targeted runs, disable the hard coverage threshold to avoid false failures:
156
+
157
+ ```console
158
+ K_SOUP_COV_MIN_HARD=false bundle exec kettle-test spec/path/to/spec.rb
140
159
  ```
141
160
 
161
+ ### Spec organization (required)
162
+
163
+ - One spec file per class/module. For each class or module under `lib/`, keep all of its unit tests in a single spec file under `spec/` that mirrors the path and file name exactly: `lib/omniauth/identity/my_class.rb` -> `spec/omniauth/identity/my_class_spec.rb`.
164
+ - Exception: Integration specs that intentionally span multiple classes. Place these under `spec/integration/` (or a clearly named integration folder), and do not directly mirror a single class. Name them after the scenario, not a class.
165
+
142
166
  ## Lint It
143
167
 
144
168
  Run all the default tasks, which includes running the gradually autocorrecting linter, `rubocop-gradual`.
@@ -153,12 +177,29 @@ Or just run the linter.
153
177
  bundle exec rake rubocop_gradual:autocorrect
154
178
  ```
155
179
 
180
+ For more detailed information about using RuboCop in this project, please see the [RUBOCOP.md](RUBOCOP.md) guide. This project uses `rubocop_gradual` instead of vanilla RuboCop, which requires specific commands for checking violations.
181
+
182
+ ### Important: Do not add inline RuboCop disables
183
+
184
+ Never add `# rubocop:disable ...` / `# rubocop:enable ...` comments to code or specs (except when following the few existing `rubocop:disable` patterns for a rule already being disabled elsewhere in the code). Instead:
185
+
186
+ - Prefer configuration-based exclusions when a rule should not apply to certain paths or files (e.g., via `.rubocop.yml`).
187
+ - When a violation is temporary, and you plan to fix it later, record it in `.rubocop_gradual.lock` using the gradual workflow:
188
+ - `bundle exec rake rubocop_gradual:autocorrect` (preferred)
189
+ - `bundle exec rake rubocop_gradual:force_update` (only when you cannot fix the violations immediately)
190
+
191
+ As a general rule, fix style issues rather than ignoring them. For example, our specs should follow RSpec conventions like using `described_class` for the class under test.
192
+
156
193
  ## Contributors
157
194
 
195
+ Your picture could be here!
196
+
158
197
  [![Contributors][🖐contributors-img]][🖐contributors]
159
198
 
160
199
  Made with [contributors-img][🖐contrib-rocks].
161
200
 
201
+ Also see GitLab Contributors: [https://gitlab.com/omniauth/omniauth-identity/-/graphs/main][🚎contributors-gl]
202
+
162
203
  ## For Maintainers
163
204
 
164
205
  ### One-time, Per-maintainer, Setup
@@ -166,46 +207,66 @@ Made with [contributors-img][🖐contrib-rocks].
166
207
  **IMPORTANT**: To sign a build,
167
208
  a public key for signing gems will need to be picked up by the line in the
168
209
  `gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there).
169
- All releases to RubyGems.org are signed releases.
210
+ All releases are signed releases.
170
211
  See: [RubyGems Security Guide][🔒️rubygems-security-guide]
171
212
 
172
213
  NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in the environment.
173
214
 
174
215
  ### To release a new version:
175
216
 
217
+ #### Automated process
218
+
219
+ 1. Update version.rb to contain the correct version-to-be-released.
220
+ 2. Run `bundle exec kettle-changelog`.
221
+ 3. Run `bundle exec kettle-release`.
222
+ 4. Stay awake and monitor the release process for any errors, and answer any prompts.
223
+
224
+ #### Manual process
225
+
176
226
  1. Run `bin/setup && bin/rake` as a "test, coverage, & linting" sanity check
177
227
  2. Update the version number in `version.rb`, and ensure `CHANGELOG.md` reflects changes
178
228
  3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
179
- 4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
180
- 5. Run `git push` to trigger the final CI pipeline before release, and merge PRs
229
+ 4. Run `bin/rake yard` to regenerate the docs site using the canonical docs task
230
+ 5. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
231
+ 6. Run `git push` to trigger the final CI pipeline before release, and merge PRs
181
232
  - NOTE: Remember to [check the build][🧪build].
182
- 6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
183
- 7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
184
- 8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
185
- 9. Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use same timestamp, and generate same checksums
233
+ 7. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
234
+ 8. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
235
+ 9. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
236
+ 10. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
237
+ - If your Bundler is >= 2.7.0, you can skip this; builds are reproducible by default.
186
238
  - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
187
239
  - If the echo above has no output, then it didn't work.
188
240
  - Note: `zsh/datetime` module is needed, if running `zsh`.
189
241
  - In older versions of `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
190
- 10. Run `bundle exec rake build`
191
- 11. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
242
+ 11. Run `bundle exec rake build`
243
+ 12. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
192
244
  to create SHA-256 and SHA-512 checksums. This functionality is provided by the `stone_checksums`
193
245
  [gem][💎stone_checksums].
194
246
  - The script automatically commits but does not push the checksums
195
- 12. Run `bundle exec rake release` which will create a git tag for the version,
196
- push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
197
-
198
- [🚎src-main]: https://github.com/omniauth/omniauth-identity
247
+ 13. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
248
+ - `sha256sum pkg/<gem name>-<version>.gem`
249
+ 14. Run `bundle exec rake release` which will create a git tag for the version,
250
+ push git commits and tags, and push the `.gem` file to the gem host configured in the gemspec.
251
+
252
+ [📜src-gl]: https://gitlab.com/omniauth/omniauth-identity
253
+ [📜src-cb]: https://codeberg.org/omniauth/omniauth-identity
254
+ [📜src-gh]: https://github.com/omniauth/omniauth-identity
199
255
  [🧪build]: https://github.com/omniauth/omniauth-identity/actions
200
256
  [🤝conduct]: https://github.com/omniauth/omniauth-identity/blob/main/CODE_OF_CONDUCT.md
201
257
  [🖐contrib-rocks]: https://contrib.rocks
202
258
  [🖐contributors]: https://github.com/omniauth/omniauth-identity/graphs/contributors
259
+ [🚎contributors-gl]: https://gitlab.com/omniauth/omniauth-identity/-/graphs/main
203
260
  [🖐contributors-img]: https://contrib.rocks/image?repo=omniauth/omniauth-identity
204
- [💎rubygems]: https://rubygems.org
261
+ [💎gem-coop]: https://gem.coop
205
262
  [🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
206
263
  [🔒️rubygems-checksums-pr]: https://github.com/rubygems/rubygems/pull/6022
207
264
  [🔒️rubygems-guides-pr]: https://github.com/rubygems/guides/pull/325
208
- [💎stone_checksums]: https://github.com/pboling/stone_checksums
265
+ [💎stone_checksums]: https://github.com/galtzo-floss/stone_checksums
209
266
  [📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
210
267
  [📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
268
+ [📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
269
+ [📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
270
+ [🚎appraisal2]: https://github.com/appraisal-rb/appraisal2
211
271
  [🏃‍♂️runner-tool-cache]: https://github.com/ruby/ruby-builder/releases/tag/toolcache
272
+ [✉️discord-invite]: https://discord.gg/3qme4XHNKN
data/FUNDING.md ADDED
@@ -0,0 +1,74 @@
1
+ <!-- RELEASE-NOTES-FOOTER-START -->
2
+
3
+ Official Discord 👉️ [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
4
+
5
+ Many paths lead to being a sponsor or a backer of this project. Are you on such a path?
6
+
7
+ [![OpenCollective Backers][🖇osc-backers-i]][🖇osc-backers] [![OpenCollective Sponsors][🖇osc-sponsors-i]][🖇osc-sponsors] [![Sponsor Me on Github][🖇sponsor-img]][🖇sponsor] [![Liberapay Goal Progress][⛳liberapay-img]][⛳liberapay] [![Donate on PayPal][🖇paypal-img]][🖇paypal]
8
+
9
+ [![Buy me a coffee][🖇buyme-small-img]][🖇buyme] [![Donate on Polar][🖇polar-img]][🖇polar] [![Donate to my FLOSS efforts at ko-fi.com][🖇kofi-img]][🖇kofi] [![Donate to my FLOSS efforts using Patreon][🖇patreon-img]][🖇patreon]
10
+
11
+ [⛳liberapay-img]: https://img.shields.io/liberapay/goal/pboling.svg?logo=liberapay&color=a51611&style=flat
12
+ [⛳liberapay]: https://liberapay.com/pboling/donate
13
+ [🖇osc-backers]: https://opencollective.com/omniauth#backer
14
+ [🖇osc-backers-i]: https://opencollective.com/omniauth/backers/badge.svg?style=flat
15
+ [🖇osc-sponsors]: https://opencollective.com/omniauth#sponsor
16
+ [🖇osc-sponsors-i]: https://opencollective.com/omniauth/sponsors/badge.svg?style=flat
17
+ [🖇sponsor-img]: https://img.shields.io/badge/Sponsor_Me!-pboling.svg?style=social&logo=github
18
+ [🖇sponsor]: https://github.com/sponsors/pboling
19
+ [🖇polar-img]: https://img.shields.io/badge/polar-donate-a51611.svg?style=flat
20
+ [🖇polar]: https://polar.sh/pboling
21
+ [🖇kofi-img]: https://img.shields.io/badge/ko--fi-%E2%9C%93-a51611.svg?style=flat
22
+ [🖇kofi]: https://ko-fi.com/pboling
23
+ [🖇patreon-img]: https://img.shields.io/badge/patreon-donate-a51611.svg?style=flat
24
+ [🖇patreon]: https://patreon.com/galtzo
25
+ [🖇buyme-small-img]: https://img.shields.io/badge/buy_me_a_coffee-%E2%9C%93-a51611.svg?style=flat
26
+ [🖇buyme]: https://www.buymeacoffee.com/pboling
27
+ [🖇paypal-img]: https://img.shields.io/badge/donate-paypal-a51611.svg?style=flat&logo=paypal
28
+ [🖇paypal]: https://www.paypal.com/paypalme/peterboling
29
+ [✉️discord-invite]: https://discord.gg/3qme4XHNKN
30
+ [✉️discord-invite-img]: https://img.shields.io/discord/1373797679469170758?style=flat
31
+
32
+ <!-- RELEASE-NOTES-FOOTER-END -->
33
+
34
+ # 🤑 A request for help
35
+
36
+ Maintainers have teeth and need to pay their dentists.
37
+ After getting laid off in an RIF in March, and encountering difficulty finding a new one,
38
+ I began spending most of my time building open source tools.
39
+ I'm hoping to be able to pay for my kids' health insurance this month,
40
+ so if you value the work I am doing, I need your support.
41
+ Please consider sponsoring me or the project.
42
+
43
+ To join the community or get help 👇️ Join the Discord.
44
+
45
+ [![Live Chat on Discord][✉️discord-invite-img-ftb]][✉️discord-invite]
46
+
47
+ To say "thanks!" ☝️ Join the Discord or 👇️ send money.
48
+
49
+ [![Sponsor omniauth/omniauth-identity on Open Source Collective][🖇osc-all-bottom-img]][🖇osc] 💌 [![Sponsor me on GitHub Sponsors][🖇sponsor-bottom-img]][🖇sponsor] 💌 [![Sponsor me on Liberapay][⛳liberapay-bottom-img]][⛳liberapay] 💌 [![Donate on PayPal][🖇paypal-bottom-img]][🖇paypal]
50
+
51
+ # Another Way to Support Open Source Software
52
+
53
+ I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small. Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions. I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).
54
+
55
+ If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in `bundle fund`.
56
+
57
+ I’m developing a new library, [floss_funding][🖇floss-funding-gem], designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.
58
+
59
+ **[Floss-Funding.dev][🖇floss-funding.dev]: 👉️ No network calls. 👉️ No tracking. 👉️ No oversight. 👉️ Minimal crypto hashing. 💡 Easily disabled nags**
60
+
61
+ [⛳liberapay-bottom-img]: https://img.shields.io/liberapay/goal/pboling.svg?style=for-the-badge&logo=liberapay&color=a51611
62
+ [🖇osc-all-img]: https://img.shields.io/opencollective/all/omniauth
63
+ [🖇osc-sponsors-img]: https://img.shields.io/opencollective/sponsors/omniauth
64
+ [🖇osc-backers-img]: https://img.shields.io/opencollective/backers/omniauth
65
+ [🖇osc-all-bottom-img]: https://img.shields.io/opencollective/all/omniauth?style=for-the-badge
66
+ [🖇osc-sponsors-bottom-img]: https://img.shields.io/opencollective/sponsors/omniauth?style=for-the-badge
67
+ [🖇osc-backers-bottom-img]: https://img.shields.io/opencollective/backers/omniauth?style=for-the-badge
68
+ [🖇osc]: https://opencollective.com/omniauth
69
+ [🖇sponsor-bottom-img]: https://img.shields.io/badge/Sponsor_Me!-pboling-blue?style=for-the-badge&logo=github
70
+ [🖇buyme-img]: https://img.buymeacoffee.com/button-api/?text=Buy%20me%20a%20latte&emoji=&slug=pboling&button_colour=FFDD00&font_colour=000000&font_family=Cookie&outline_colour=000000&coffee_colour=ffffff
71
+ [🖇paypal-bottom-img]: https://img.shields.io/badge/donate-paypal-a51611.svg?style=for-the-badge&logo=paypal&color=0A0A0A
72
+ [🖇floss-funding.dev]: https://floss-funding.dev
73
+ [🖇floss-funding-gem]: https://github.com/galtzo-floss/floss_funding
74
+ [✉️discord-invite-img-ftb]: https://img.shields.io/discord/1373797679469170758?style=for-the-badge
data/LICENSE.md ADDED
@@ -0,0 +1,10 @@
1
+ # License
2
+
3
+ This project is made available under the following license.
4
+ Choose the option that best fits your use case:
5
+
6
+ - [MIT](MIT.md)
7
+
8
+ ## Copyright Notice
9
+
10
+ - Copyright (c) 2025-2026 |7eter l-|. l3oling