Skip to content

chore: migrate VSCode settings to @peerigon/configs#178

Closed
jhnns wants to merge 2 commits intomainfrom
chore/migrate-vscode-settings
Closed

chore: migrate VSCode settings to @peerigon/configs#178
jhnns wants to merge 2 commits intomainfrom
chore/migrate-vscode-settings

Conversation

@jhnns
Copy link
Member

@jhnns jhnns commented Jul 28, 2025

Summary

  • Updated .vscode/settings.json to use the shared configuration from @peerigon/configs
  • This includes additional settings for search exclusions, file nesting patterns, and JavaScript/TypeScript preferences
  • All tests pass with the new configuration

Test plan

  • Verified ESLint still works with npm run test:lint
  • Verified Prettier formatting works with npm run test:format
  • Verified TypeScript compilation works with npm run test:types

🤖 Generated with Claude Code

gitbutler-client and others added 2 commits May 9, 2025 11:41
This is placeholder commit and will be replaced by a merge of yourvirtual branches.

Due to GitButler managing multiple virtual branches, you cannot switch back and
forth between git branches and virtual branches easily. 

If you switch to another branch, GitButler will need to be reinitialized.
If you commit on this branch, GitButler will throw it away.

For more information about what we're doing here, check out our docs:
https://docs.gitbutler.com/features/virtual-branches/integration-branch
🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@jhnns jhnns closed this Jul 28, 2025
@jhnns jhnns deleted the chore/migrate-vscode-settings branch July 29, 2025 21:08
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.

2 participants