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

yaml.schemas and Setting sync conflicts #155

Open
SailorMax opened this issue Feb 27, 2025 · 0 comments
Open

yaml.schemas and Setting sync conflicts #155

SailorMax opened this issue Feb 27, 2025 · 0 comments

Comments

@SailorMax
Copy link

SailorMax commented Feb 27, 2025

Describe the bug
When use "Jira and Bitbucket" on different VSCodes of different system users System sync always output merge conflict in settings file, because of your "yaml.schemas" settings, which has absolute path to user's profile directory + version of extension.

To Reproduce
Steps to reproduce the behavior:

  1. Setup for two different users VSCode with "Jira and Bitbucket"
  2. Setup both VSCodes to same Microsoft account
  3. Open first and sync settings
  4. Open second and sync settings

Expected behavior
No problem sync

Environment and Version (please complete the following information):

  • Atlassian Plugin Version (3.4.11)
  • Visual Studio Code Version (1.97.2)
  • Is this a local or cloud environment? (Local)
  • If Local, OS (Windows)

Additional context
VSCode has variables for home directory: https://code.visualstudio.com/docs/editor/profiles#_common-questions
And version you can hide inside the json or make it handler more flexible.

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

No branches or pull requests

1 participant