-
Notifications
You must be signed in to change notification settings - Fork 15
docs: improve readability in Features section #87
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -8,8 +8,8 @@ functionality with automated setup, branch tracking, and project-specific hooks. | |||||
| ### 🚀 No More Path Gymnastics | ||||||
|
|
||||||
| **git-worktree pain:** | ||||||
| `git worktree add ../project-worktrees/feature/auth feature/auth` **wtp | ||||||
| solution:** `wtp add feature/auth` | ||||||
| `git worktree add ../project-worktrees/feature/auth feature/auth`<br> | ||||||
| **wtp solution:** `wtp add feature/auth` | ||||||
|
|
||||||
| wtp automatically generates sensible paths based on branch names. Your | ||||||
| `feature/auth` branch goes to `../worktrees/feature/auth` - no redundant typing, | ||||||
|
|
@@ -18,7 +18,8 @@ no path errors. | |||||
| ### 🧹 Clean Branch Management | ||||||
|
|
||||||
| **git-worktree pain:** Remove worktree, then manually delete the branch. Forget | ||||||
| the second step? Orphaned branches accumulate. **wtp solution:** | ||||||
| the second step? Orphaned branches accumulate.<br> | ||||||
|
||||||
| the second step? Orphaned branches accumulate.<br> | |
| the second step? Orphaned branches accumulate.<br> |
Copilot
AI
Feb 11, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The newline before this “wtp solution” label may not render as a line break in Markdown (it’s treated as whitespace within the same paragraph). If the goal is visual separation, add a blank line before the label or use a hard line break.
| migrations → Finally start coding<br> | |
| migrations → Finally start coding<br> |
Copilot
AI
Feb 11, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Markdown will usually collapse the newline before this label into a space, so the “wtp solution” text may still render inline with the preceding line. Add a blank line or a hard line break to reliably force the visual separation.
| path)<br> | |
| path)<br> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In GitHub-flavored Markdown, a single newline inside a paragraph is rendered as a space. As written, this likely won’t create a visible line break between the command and the “wtp solution” label. To ensure the intended separation, add a blank line between them or use a hard line break (two trailing spaces or
<br>).