maint: general jupyterhub org repo maintenance updates #221
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
This reverts commit d3acf4e.
consideRatio
force-pushed
the
pr/general-maint
branch
from
1a65d7e to
38485d5
Compare
consideRatio
force-pushed
the
pr/general-maint
branch
from
b992832 to
f8a035c
Compare
for more information, see https://pre-commit.ci
minrk
approved these changes
Jun 5, 2023
Member
Author
|
Thanks @minrk! Going for a merge |
Member
Author
|
Hmmm, github bugged, making it merged in git, but not the PR. Well the latest commit 586f336 in this PR is now merged into main branch. This PR may not show up in the github-activity changelog, or maybe, I'm not sure. |
echarles
pushed a commit
to datalayer-externals/jupyterhub-auth-ldap
that referenced
this pull request
Jun 5, 2023
maint: general jupyterhub org repo maintenance updates
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.
This is a maintenance catch-up PR, aligning it with practices as they have developed over time in the jupyterhub org.