vscode-file-nesting-config

Description Use the timestamp embedded in the upstream README config block for the generated marker instead of formatting the local update time with . Before this change, the extension rewrote the marker with each machine's local locale, for example: When VS Code/Cursor settings are synced across Windows and macOS (via Settings Sync, dotfiles, or a git-tracked ), the same upstream file-nesting config can therefore create platform-specific churn and merge conflicts even when the actual nesting patterns are identical. This keeps the previous marker shape () but makes the value deterministic by reusing the upstream README timestamp, for example: The marker is not used for file-nesting parsing or config comparison: the extension already removes the marker before comparing local patterns, while the upstream README parser strips JSONC comment lines before . Linked Issues N/A. No exact existing issue/PR was found for the locale-specific update marker; related updater behavior discussions include #127 and #218. Verification Parsed the current README config block with Node to verify the upstream timestamp and JSON extraction still work.

Please be aware that vibe-coding contributions are 🚫 STRICTLY PROHIBITED. We are humans behind these open source projects, trying hard to maintain good quality and a healthy community. Not only do vibe-coding contributions pollute the code, but they also drain A LOT of unnecessary energy and time from maintainers and toxify the community and collaboration. All vibe-coded, AI-generated PRs will be rejected and closed without further notice. In severe cases, your account might be banned organization-wide and reported to GitHub. PLEASE SHOW SOME RESPECT and do not do so. Before submitting the PR, please make sure you do the following: Read the Contributing Guide. Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate. Provide a description in this PR that addresses what the PR is solving and WHY**, or reference the issue that it solves (e.g. ). Ideally, include relevant tests that fail without this PR but pass with it. [x]

Clear and concise description of the problem is the config file of Microsoft Live Share, see here. Suggested solution It should be collapsed but I don't know where it should be Alternative _No response_ Additional context _No response_ Validations [X] Follow our Code of Conduct [X] Read the Contributing Guide. [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.