-
-
Couldn't load subscription status.
- Fork 4.6k
fix: check if properties exist before using them #52778
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: check if properties exist before using them #52778
Conversation
|
/backport to 31 |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
4530184 to
ebd80bc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐘
|
The backport to # Switch to the target branch and update it
git checkout 31
git pull origin 31
# Create the new backport branch
git checkout -b backport/52778/31
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick ebd80bc1
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/52778/31Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/52778/31') Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
/backport to stable31 |
|
When you miss type the branch name in the backport commad 🫏 🫏 |
|
Is it possible to backport this PR to 30? |
@SebastianKrupinski Is there a reason for not backporting further, for example, the fixed code is missing on |
|
/backport to stable30 |
There was a reason, but I don't remember the reason now, I'll backport it this morning. |
Resolves:
Summary
Checklist