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

Set pin state correct after rename #3432

Merged
merged 1 commit into from
Jun 14, 2021

Conversation

FlexW
Copy link

@FlexW FlexW commented Jun 11, 2021

No description provided.

@FlexW FlexW force-pushed the bugfix/set-pin-state-correct-after-rename branch from 8b8c944 to 77a4668 Compare June 11, 2021 15:01
Copy link
Collaborator

@mgallien mgallien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch I did the same change a few lines down.

@FlexW
Copy link
Author

FlexW commented Jun 14, 2021

/rebase

Fixes #3403 #3082 #3391

Signed-off-by: Felix Weilbach <felix.weilbach@nextcloud.com>
@github-actions github-actions bot force-pushed the bugfix/set-pin-state-correct-after-rename branch from 77a4668 to a89a84f Compare June 14, 2021 13:40
@nextcloud-desktop-bot
Copy link

AppImage file: Nextcloud-PR-3432-a89a84ff14565f09bca5909ccbfe163919a21038-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

Please make sure to quit your existing Nextcloud app and backup your data.

@FlexW FlexW merged commit 3542d17 into master Jun 14, 2021
@FlexW FlexW deleted the bugfix/set-pin-state-correct-after-rename branch June 14, 2021 13:49
@FlexW
Copy link
Author

FlexW commented Jun 14, 2021

/backport stable-3.2

1 similar comment
@FlexW
Copy link
Author

FlexW commented Jun 14, 2021

/backport stable-3.2

@FlexW
Copy link
Author

FlexW commented Jun 14, 2021

/backport to stable-3.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants