TTT Editor (Terminal Text Tool): A real alternative to VS Code, Zed, and Sublime that runs in your terminal. A TUI that feels like GUI. Single binary, zero config.
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 79%
Response Time: 7d
First Timer Success: 60%
eugenioenko/ttt has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eugenioenko/ttt respond to incoming external pull requests in approximately 164.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 69.9 places eugenioenko/ttt in the A tier.
The external contributor pull request merge rate for eugenioenko/ttt is 79.0%, based on public PR activity from non-core contributors.
eugenioenko/ttt currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in eugenioenko/ttt.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/eugenioenko/ttt?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~107 hours (96% approval). Large PRs (>500 lines) take ~789 hours (36% approval). Keep your diff compact for rapid review.
Description Add a "New Branch" option to the Changes panel's more menu (... button) that lets users create a new git branch without leaving the panel. Context The Changes panel menu currently has Pull, Push, and Sync actions but no way to create a new branch. Users often want to create a branch right before committing, and having to go through the command palette breaks the flow. Implementation notes Add a "New Branch" entry to BuildChangesPanelMenu() in internal/app/callbacks.go, grouped with the existing Pull/Push/Sync items The handler should open an input dialog asking for the branch name, similar to how "Add Folder" and "Open PR Diff" work (see ShowInputDialog usage in the codebase) On submit, run git checkout -b <name> via the existing RepoTask pattern Look at how Pull/Push/Sync are wired in internal/app/commands_git.go and internal/app/repo_ops.go for the async pattern The git operation itself can be added to internal/git/git.go (e.g. func CheckoutNewBranch(dir, name string) er
With appearance.icons set to nerd-font, file-type icons (internal/fileicons) only show in the explorer and the changes panel. fileicons is imported in just explorer.go, changes_tree.go and file_icons.go. Places that still show plain file names: Editor tabs (most visible) Global search results (file rows) Ctrl+P file picker Commit detail file list PR file lists, if not already covered by the changes tree Expected: the same glyph and theme color as the explorer, resolved through fileicons.ForFile and fileIconStyle, and following appearance.icons (live toggle, no restart). Notes: Widths: use textwidth for any layout that includes the glyph (tab widths, truncation). Tab bar hit-testing and reorder math must account for the extra icon column.
TerminalWidget.Render can draw a fullwidth rune in the last content column. When the scrollbar is showing, contentW is w - 1, and both render loops (live view and scrollback) copy every cell to surface.SetCell unchanged, so a wide rune at x == contentW-1 is handed to the surface as-is. AGENTS.md says a fullwidth rune must never be drawn in the last column of a clip region: the terminal paints it across two columns regardless of clipping, so it can bleed over the scrollbar or border to its right. DrawText already substitutes a space in that case; the terminal widget does not. Where internal/ui/terminal_widget.go, the two for x := 0; x < contentW ... loops in Render. Notes Not a regression from #635. The loops passed cells to SetCell the same way before that PR; it was raised in review of it (CodeRabbit). Not reproduced yet. A repro would be a terminal with scrollback (so the scrollbar shows) and a line of CJK text whose last wide rune lands in the last content column. Suggested fix In
golangci-lint errcheck is currently disabled (~50 violations). Enable it and fix all unchecked error returns. See PR #477 for context.
When opening a file with restricted permissions (e.g., chmod 444), there is no visual indicator that the file is read-only. The file can be edited and saved without warning. Expected behavior Show a read-only indicator in the tab title (lock icon or "(read-only)") or status bar Warn or block save for read-only files unless the user explicitly chooses to overwrite Notes On Linux, atomic save (temp file + rename) can succeed even for 444 files when the containing directory is writable, so the user unknowingly overwrites a read-only file From QA BUG-019.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to eugenioenko/ttt, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of eugenioenko/ttt acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.0% were successfully merged into the primary branch.
eugenioenko/ttt has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 69.9 places eugenioenko/ttt in the Welcoming tier.
The external pull request merge rate is 79.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eugenioenko/ttt currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for eugenioenko/ttt are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.