Skip to content

Conversation

@codewithtyler
Copy link
Collaborator

@codewithtyler codewithtyler commented Dec 15, 2024

The suggested change here is for the person reporting the bug to make their Bolt project public so that it's easier for someone trying to help to see if they can tell what the problem is. By having the project public this would save a bit of back and forth in communication between the maintainer and the person submitting the bug report.

image

Copy link
Member

@AriPerkkio AriPerkkio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @codewithtyler, this change is very welcome!

Maybe we could also have a picture that shows how to do this? I think this picture could be used: https://github.com/stackblitz/bolt.new/issues/3894#issuecomment-2527183627

We could also have a required checkbox with text I have made my project public or accessible by URL [x], like this: https://github.com/vitest-dev/vitest/blob/4e60333dc7235704f96314c34ca510e3901fe61f/.github/ISSUE_TEMPLATE/bug_report.yml?plain=1#L45-L52

@codewithtyler
Copy link
Collaborator Author

haha @AriPerkkio I thought you might like this change.

@codewithtyler
Copy link
Collaborator Author

Sorry for the multiple commits. GitHub kept pointing me to the wrong line with the file. It kept saying line 2 was the issue when it was really line 33.

Copy link
Member

@AriPerkkio AriPerkkio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@AriPerkkio AriPerkkio merged commit eda10b1 into stackblitz:main Dec 17, 2024
2 checks passed
@codewithtyler codewithtyler deleted the patch-1 branch December 17, 2024 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants