Skip to content

Use Git branch names for trace saves#84

Open
wndzph9jkb-create wants to merge 1 commit into
tsperf:mainfrom
wndzph9jkb-create:issue-20-git-branch-save
Open

Use Git branch names for trace saves#84
wndzph9jkb-create wants to merge 1 commit into
tsperf:mainfrom
wndzph9jkb-create:issue-20-git-branch-save

Conversation

@wndzph9jkb-create

Copy link
Copy Markdown

Summary

  • Add an opt-in tsperf.tracer.useGitBranchSaveName setting.
  • When enabled, initialize the trace save name from the active VS Code Git repository's current branch or detached HEAD.
  • Sanitize Git labels before using them as storage directory names.
  • Fall back to the existing default save when Git is unavailable or has no HEAD label.

Why

Closes #20.

Using the current Git branch as the default save name keeps trace files and trace diagnostics aligned with the checked-out code, especially when switching between branches during performance investigations.

Validation

  • corepack pnpm typecheck
  • corepack pnpm lint
  • corepack pnpm exec vitest run
  • corepack pnpm run generate:contributes
  • cd srcDev && corepack pnpm exec rollup -c
  • corepack pnpm exec nuxt build ui
  • corepack pnpm exec rollup -c

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.

Add settings to use git branch for current save

1 participant