fix: restore labels, codicon aliases, and issue branch flow#39
Merged
FanaticPythoner merged 3 commits intoMay 30, 2026
Conversation
Prefix-only regex matches that contain ($TAGS) keep the physical-line
suffix available to displayText and ${after} across editor and workspace scans.
Detection:
- extend non-multiline ($TAGS) regex matches to the physical line end before tag extraction
- preserve whole-match tags for explicit regexes without ($TAGS)
- cover legacy prefix regex, default labels, and workspace normalization
Icons:
- generate codicon alias names instead of codepoints
- parse "$(icon)" syntax through a shared helper for tree, gutter, and configuration checks
- keep malformed codicon syntax invalid before alias lookup
Workflow:
- add issue-derived branch recipes for full flow and standalone branch steps
- derive default branch names from GitHub issue numbers and titles
- create local and remote branches from upstream master without pushing master
- move source-branch changes onto the issue branch, stage them, wait for commit, then push the issue branch
- prompt for PR creation after branch push with yes as the default answer
Docs and artifacts:
- document prefix-only regex suffix rendering and octicon/codicon icon syntax
- replace checked-in perf JSON with markdown benchmark summaries
- ignore generated perf JSON artifacts
Fixes #28
Fixes #36
Issue branch staging now transfers only the source branch index while rejecting unstaged tracked edits and untracked files before branch switch. Branch workflow: - create issue branches without temporary origin/master tracking - keep issue branch upstreams pointed at origin/<branch> - reject non-project issue URLs and non-master base branches - force pull requests to FanaticPythoner/better-todo-tree master - pass explicit gh repo, base, and head arguments to skip fork prompts
Resolves an issue where extracted text from block comments (e.g., multi-line, HTML) incorrectly included the trailing comment delimiters (`*/`, `-->`). This change introduces new utility functions to accurately identify and remove these trailing end tokens from the detected match text. The new `trimTrailingEndToken` and `trimTrailingMultiLineCommentEnd` functions are integrated into the match normalization process, ensuring that the `displayText` and `after` properties only contain the relevant comment content. To support this, a `resolveBlockCommentPattern` utility centralizes the logic for determining the correct block comment pattern for a given file type, including language aliases (e.g., Markdown to HTML, Haskell to C++). Fixes #28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prefix-only regex matches that contain ($TAGS) keep the physical-line
suffix available to displayText and ${after} across editor and workspace scans.
Detection:
Icons:
Workflow:
Docs and artifacts:
Fixes #28
Fixes #36