Check in collect_env.py to improve UX of GitHub Issue reporting #8692
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
During my oncall shift, I noticed that not just one user forget to include the dev env when report GitHub issues to us (issue1, issue2). And they are not aware of that the script is not included in the repo by default and they have to download it separately (#8684 (comment)).
I think a better UX, to make it easier for both us and users, we should make the process easier by including the script in our repo. So in this PR, we check in the
collect_env.py
toutil/
and update the guide in issue template.Test plan
python util/collect_env.py
locally