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

Incorrect work of the plugin when working in two or more open logseq windows with different repos #34

Closed
dimonbavly opened this issue Jul 5, 2023 · 2 comments · Fixed by #35
Labels

Comments

@dimonbavly
Copy link

I have to work with two or more logseq windows open. In one window, one git repository is configured, in the other, - another. But when switching between windows, only one repository works in the extension. The one whose window was opened later. Please fix this bug.

@dimonbavly
Copy link
Author

That is, to be more precise - in both windows, it turns out that the repository works from the last opened window.

k2s added a commit to k2s/logseq-plugin-git that referenced this issue Jul 22, 2023
…ady performing

fix commitAndPush was showing error if there were no changes to be committed
fix haydenull#34 will use correct git folder if multiple windows are open
@k2s k2s mentioned this issue Jul 22, 2023
haydenull pushed a commit that referenced this issue Jul 26, 2023
…ady performing

fix commitAndPush was showing error if there were no changes to be committed
fix #34 will use correct git folder if multiple windows are open
haydenull pushed a commit that referenced this issue Jul 26, 2023
…eady performing

fix: commitAndPush was showing error if there were no changes to be committed
fix: #34 will use correct git folder if multiple windows are open
github-actions bot pushed a commit that referenced this issue Jul 26, 2023
## [1.5.3](v1.5.2...v1.5.3) (2023-07-26)

### Bug Fixes

* [#30](#30), shortcut mod+alt+s will pull rebase ([5f42bd5](5f42bd5))
* stack git operations not to get errors when auto actions are already performing ([e78bb2c](e78bb2c)), closes [#34](#34)
@github-actions
Copy link

🎉 This issue has been resolved in version 1.5.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

1 participant