since we can use unicode, we should have proper icons before issues to denote the type. those icons should have different colors for different types. also the lhome page should lnclude the title for issue acitvities and pull request issues and commits, jusst shortened to fit in the screen area of the activity overview.
since we can use unicode, we should have proper icons before issues to denote the type. those icons should have different colors for different types. also the lhome page should lnclude the title for issue acitvities and pull request issues and commits, jusst shortened to fit in the screen area of the activity overview.
hugo
added this to the first public update release milestone 2026-08-15 08:58:03 +00:00
Added distinct colored Unicode icons for repository, issue, pull request, branch, tag, push/commit, and release activities.
Home activity rows now resolve and cache the real issue and pull-request titles, use the real commit subject for push activity, and retain the existing navigation targets.
Titles are truncated by terminal display width so icons and text stay inside the activity pane.
Live TUI against the configured Gitea feed: the #67 comment and close events both rendered the real issue title (not the comment body), the push event rendered Add tagged CLI and TUI releases (#67), distinct icons were visible, long titles were ellipsized, and an automatic refresh completed successfully.
Implemented in `e5131f6`.
- Added distinct colored Unicode icons for repository, issue, pull request, branch, tag, push/commit, and release activities.
- Home activity rows now resolve and cache the real issue and pull-request titles, use the real commit subject for push activity, and retain the existing navigation targets.
- Titles are truncated by terminal display width so icons and text stay inside the activity pane.
Verification:
- `cargo build -p gotcha-tui`
- `cargo fmt --all -- --check`
- `RUSTFLAGS="-D warnings" cargo check --workspace --all-targets`
- `cargo clippy --workspace --all-targets -- -D warnings`
- `cargo test --workspace`
- Live TUI against the configured Gitea feed: the #67 comment and close events both rendered the real issue title (not the comment body), the push event rendered `Add tagged CLI and TUI releases (#67)`, distinct icons were visible, long titles were ellipsized, and an automatic refresh completed successfully.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
since we can use unicode, we should have proper icons before issues to denote the type. those icons should have different colors for different types. also the lhome page should lnclude the title for issue acitvities and pull request issues and commits, jusst shortened to fit in the screen area of the activity overview.
Implemented in
e5131f6.Verification:
cargo build -p gotcha-tuicargo fmt --all -- --checkRUSTFLAGS="-D warnings" cargo check --workspace --all-targetscargo clippy --workspace --all-targets -- -D warningscargo test --workspaceAdd tagged CLI and TUI releases (#67), distinct icons were visible, long titles were ellipsized, and an automatic refresh completed successfully.