fix(autocomplete): respect privacy settings for sharing#12715
Conversation
|
@ChristophWurst I've been actually wondering if we want to always allow full sab access to phishing detection check? maybe without exposing the actual contact ? |
Signed-off-by: Hamza <hamzamahjoubi221@gmail.com>
ab013c7 to
b7e6088
Compare
|
/backport to stable5.7 |
|
/backport to stable5.6 |
|
/backport to stable5.5 |
|
/backport to stable3.7 |
|
The backport to # Switch to the target branch and update it
git checkout stable3.7
git pull origin stable3.7
# Create the new backport branch
git checkout -b backport/12715/stable3.7
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick b7e60882
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/12715/stable3.7Error: Failed to check for changes with origin/stable3.7: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # Switch to the target branch and update it
git checkout stable5.5
git pull origin stable5.5
# Create the new backport branch
git checkout -b backport/12715/stable5.5
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick b7e60882
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/12715/stable5.5Error: Failed to check for changes with origin/stable5.5: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # Switch to the target branch and update it
git checkout stable5.6
git pull origin stable5.6
# Create the new backport branch
git checkout -b backport/12715/stable5.6
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick b7e60882
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/12715/stable5.6Error: Failed to check for changes with origin/stable5.6: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # Switch to the target branch and update it
git checkout stable5.7
git pull origin stable5.7
# Create the new backport branch
git checkout -b backport/12715/stable5.7
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick b7e60882
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/12715/stable5.7Error: Failed to check for changes with origin/stable5.7: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
/backport to stable5.7 please |
|
The backport to # Switch to the target branch and update it
git checkout stable5.7
git pull origin stable5.7
# Create the new backport branch
git checkout -b backport/12715/stable5.7
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick b7e60882
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/12715/stable5.7Error: Failed to check for changes with origin/stable5.7: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
How to test:
@the mention shortcut in composerrespect them