Open skorfmann opened 1 year ago
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Feature Spec
Provide a single command in the wing cli to make gathering of local context for bug / issue reporting a streamlined experience.
something like:
wing env
orwing bug-env
or some actually good name, which would just print out whatever information makes sense for reproducing problems and is ready to copy & paste. e.g.Perhaps target specific infos?
perhaps pre-formatted for github issues? (e.g. markdown table) and a direct link to create a bug ticket
Use Cases
When creating bugs / issues it would be great to have detailed context information. Even just the currently requested info in bug tickets of: wing / console / node version and OS would be nice to wrap into a simple helper command. Beyond that, things like listing installed packages from a potentially present
package.json
could be nice.Implementation Notes
No response
Component
CLI
Community Notes