8000 Command to help file bug reports · Issue #4873 · git-town/git-town · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Command to help file bug reports #4873

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.

Sign up for GitHub

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

Jump to bottom
Open
kevgo opened this issue May 7, 2025 · 1 comment
Open

Command to help file bug reports #4873

kevgo opened this issue May 7, 2025 · 1 comment

Comments

@kevgo
Copy link
Contributor
kevgo commented May 7, 2025 •
edited
Loading

Currently very few people send proper bug reports because Git Town makes it hard to do so. When somebody experiences a problem with a Git Town command, they are required to send the output of the command using --verbose. This requires re-running the command, which is extra effort and often not even possible.

Git Town could help make this easier by printing something that people can copy-and-paste into a bug report.

  • the output of the last command as if it was run using --verbose
  • the branch lineage

Possible names for the new command:

  • git town bug-report
  • git town what-happened
  • git town last-command-verbose
  • git town log
  • git town log --last

Implementation:

  • store the output of all commands (frontend and backend) in a log file that exists next to the runstate file
@kevgo kevgo changed the title Command to re-print the output of the last command in verbose mode Command to help file bug reports May 8, 2025
@kevgo
Copy link
Contributor Author
kevgo commented May 8, 2025

A challenge with this is that it would require capturing the output of frontend commands. Right now they stream to the terminal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kevgo
0