Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: prevent error when enpty data from backend #4520

Merged
merged 1 commit into from
Jan 28, 2025

Conversation

vitormattos
Copy link
Member

No description provided.

@vitormattos vitormattos added this to the Next Major (32) milestone Jan 28, 2025
@vitormattos vitormattos self-assigned this Jan 28, 2025
@vitormattos vitormattos merged commit 01cfca0 into main Jan 28, 2025
58 checks passed
@vitormattos vitormattos deleted the fix/prevent-error-when-empty-data-from-backend branch January 28, 2025 18:50
@vitormattos
Copy link
Member Author

/backport to stable31

@vitormattos
Copy link
Member Author

/backport to stable30

@vitormattos
Copy link
Member Author

/backport to stable29

@backportbot-libresign
Copy link

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

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

# Create the new backport branch
git checkout -b backport/4520/stable31

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

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

Error: No changes found in backport branch


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

@LibreSign LibreSign deleted a comment from backportbot-libresign bot Jan 28, 2025
@LibreSign LibreSign deleted a comment from backportbot-libresign bot Jan 28, 2025
@LibreSign LibreSign deleted a comment from backportbot-libresign bot Jan 28, 2025
@backportbot-libresign
Copy link

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

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

# Create the new backport branch
git checkout -b backport/4520/stable30

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

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

Error: No changes found in backport branch


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

@backportbot-libresign
Copy link

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/4520/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 2df189dd

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/4520/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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant