feat(service): add project.lock_status endpoint #2531
Merged
Conversation
This file contains 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
m-alisafaee
force-pushed
the
2507-lock-status-endpoint
branch
from
237130e
to
4607651
Compare
|
You can access the deployment of this PR at https://renku-ci-rp-2531.dev.renku.ch |
lorenzo-cavazzi
approved these changes
Dec 20, 2021
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.
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.
Description
project.lock_statusendpoint which returns whether a project is locked for writing or not.1.0the default version.NOTE: When a project is not in the cache or the project_id/git_url is not found, this will NOT raise an error and just returns false (i.e. not locked).
Fixes #2507
Fixes #2532
/deploy renku-ui=1.0-next