Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign up[ruby] Update omniauth-rails_csrf_protection: 0.1.1 → 0.1.2 (minor) #306
+1
−1
Conversation
depfu
bot
added
the
depfu
label
Jun 5, 2019
This comment has been minimized.
This comment has been minimized.
codecov-io
commented
Jun 5, 2019
•
Codecov Report
@@ Coverage Diff @@
## master #306 +/- ##
=======================================
Coverage 89.33% 89.33%
=======================================
Files 35 35
Lines 619 619
=======================================
Hits 553 553
Misses 66 66 Continue to review full report at Codecov.
|
ruebot
merged commit 559f703
into
master
Jun 5, 2019
depfu
bot
deleted the
depfu/update/omniauth-rails_csrf_protection-0.1.2
branch
Jun 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
depfu bot commentedJun 5, 2019
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Release Notes
0.1.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
Bump to 0.1.2
Merge pull request #2 from kobsy/dup-env
Avoided modifying env
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands