Skip to content

Conversation

@joshtrichards
Copy link
Member

πŸ“ Summary

In case needed to troubleshoot situations involving permissions, locking, etc. Addresses post-merger review comments:

#5948 (comment)

#6155 (comment)

πŸ–ΌοΈ Screenshots

🏚️ Before 🏑 After
B A

🚧 TODO

  • ...

🏁 Checklist

  • Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
  • Sign-off message is added to all commits
  • Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests
  • Documentation (README or documentation) has been updated or is not required

@joshtrichards
Copy link
Member Author

/backport to stable30

@joshtrichards
Copy link
Member Author

/backport to stable29

@juliusknorr juliusknorr merged commit ac8f529 into main Nov 21, 2024
65 checks passed
@juliusknorr juliusknorr deleted the fix/workspace-exception-debug-logging branch November 21, 2024 19:12
@backportbot
Copy link

backportbot bot commented Nov 21, 2024

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/6675/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 9df5c08a

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/6675/stable29

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants