Enable token refresh for Gitlab #422
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #422 +/- ##
==========================================
+ Coverage 96.35% 96.36% +0.01%
==========================================
Files 37 37
Lines 1070 1073 +3
==========================================
+ Hits 1031 1034 +3
Misses 39 39
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Contributor
Author
|
Pinned pillow to 9.5 based on https://bugs.launchpad.net/tacker/+bug/2026345 |
Collaborator
Ah, nice catch. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gitlab removed support for optionally expiring tokens in Gitlab 15.0. Adding in the refresh as optional since there may be self hosted instances in the wild older then 15.0.
https://docs.gitlab.com/ee/integration/oauth_provider.html#access-token-expiration