Skip to content

Conversation

@ChristophWurst
Copy link
Member

This fixes red Psalm CI after nextcloud/server#49882.

@ChristophWurst
Copy link
Member Author

/backport to stable4.2

@ChristophWurst
Copy link
Member Author

/backport to stable3.7

@ChristophWurst ChristophWurst force-pushed the fix/json-response-status-codes branch from 16394de to 5620710 Compare January 9, 2025 05:59
@ChristophWurst ChristophWurst merged commit e9c7893 into main Jan 9, 2025
35 checks passed
@ChristophWurst ChristophWurst deleted the fix/json-response-status-codes branch January 9, 2025 08:07
@backportbot
Copy link

backportbot bot commented Jan 9, 2025

The backport to stable4.2 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable4.2
git pull origin stable4.2

# Create the new backport branch
git checkout -b backport/10550/stable4.2

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/10550/stable4.2

Error: Failed to clone repository: Failed to checkout branches: fatal: ambiguous argument 'origin/stable4.2': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'


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

@ChristophWurst
Copy link
Member Author

/backport to stable4.1

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

Projects

Status: ☑️ Done

Development

Successfully merging this pull request may close these issues.

4 participants