feat(Sharing): Add per-recipient permissions - #63854
Merged
Merged
Conversation
…deleting all shares Signed-off-by: provokateurin <kate@provokateurin.de>
…omatically Signed-off-by: provokateurin <kate@provokateurin.de>
Signed-off-by: provokateurin <kate@provokateurin.de>
…s to helper methods Signed-off-by: provokateurin <kate@provokateurin.de>
…nType Signed-off-by: provokateurin <kate@provokateurin.de>
…Permission in favor of updateShareProperty and updateSharePermission Signed-off-by: provokateurin <kate@provokateurin.de>
Signed-off-by: provokateurin <kate@provokateurin.de>
provokateurin
requested review from
CarlSchwan,
icewind1991,
skjnldsv and
susnux
August 31, 2026 12:53
provokateurin
requested review from
Altahrim and
sorbaugh
and removed request for
a team
August 31, 2026 12:53
Member
Author
|
/backport to stable35 |
icewind1991
reviewed
Aug 31, 2026
icewind1991
reviewed
Aug 31, 2026
provokateurin
force-pushed
the
unified-sharing-per-recipient-permissions
branch
from
September 1, 2026 06:18
47701b0 to
52595d0
Compare
Signed-off-by: provokateurin <kate@provokateurin.de>
…ingBackend Signed-off-by: provokateurin <kate@provokateurin.de>
provokateurin
force-pushed
the
unified-sharing-per-recipient-permissions
branch
from
September 1, 2026 13:53
52595d0 to
4d05a09
Compare
Member
Author
|
@icewind1991 I did one more small thing which is that the check for effective permissions is only done when you want to grant a permission to a recipient. If you yourself are denied a permission, you can deny it for a child recipient of yours. |
icewind1991
approved these changes
Sep 1, 2026
provokateurin
enabled auto-merge
September 1, 2026 14:00
susnux
approved these changes
Sep 1, 2026
Contributor
|
/backport to stable35 |
3 tasks
|
The backport to # Switch to the target branch and update it
git checkout stable35
git pull origin stable35
# Create the new backport branch
git checkout -b backport/63854/stable35
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 362d7365 3e838a2f 48025f62 d0a62e0b fc064129 5567e142 3e9f34ea 5bb0bc0e 4d05a092
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/63854/stable35Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/63854/stable35."} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
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
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.
No description provided.