Skip to content
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.

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

GitHub issue template with repros via GitHub Actions #947

Merged
merged 2 commits into from
Feb 4, 2020

Conversation

cspotcode
Copy link
Collaborator

@cspotcode cspotcode commented Jan 24, 2020

Related: #492

I had an idea to facilitate repros via Github Actions.

I setup a repository with Github Actions set to run a shell script. The idea is you can open a PR on that repository, modifying the code however you need to reproduce an issue. Github Actions will automatically run the reproduction.

One benefit is that reporters don't need to create their own git repository to post a reproduction. We offer a preconfigured repo for them to fork, paste their code, and push. Or for really simple cases, people might even be able to post their repro using Github's web UI.

https://github.com/cspotcode/ts-node-repros

@coveralls
Copy link

coveralls commented Jan 24, 2020

Coverage Status

Coverage remained the same at 78.864% when pulling b48afd8 on issue-template into 8ac4be5 on master.

https://gist.github.com/Rich-Harris/88c5fc2ac6dc941b22e7996af05d70ff

You can create a reproduction here:
https://github.com/cspotcode/ts-node-repros
Copy link
Member

Choose a reason for hiding this comment

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

Do you want to move this under TypeStrong too?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, that'd be ideal.

Copy link
Collaborator Author

@cspotcode cspotcode Jan 27, 2020

Choose a reason for hiding this comment

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

@blakeembrey what's the best way to do this? Push the code to TypeStrong/ts-node-repros? Or use Github's "Transfer Ownership" button?

### Steps to reproduce the problem



Copy link
Member

Choose a reason for hiding this comment

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

Nit: Let's use the same three white spaces for each section?

@cspotcode
Copy link
Collaborator Author

I tried to transfer the repository to TypeStrong, but Github showed me this message: "You don’t have the permission to create public repositories on TypeStrong"

@blakeembrey
Copy link
Member

@cspotcode Invited you to the org, sorry for the delay. That should let you transfer.

@cspotcode cspotcode merged commit d578e17 into master Feb 4, 2020
@cspotcode
Copy link
Collaborator Author

@blakeembrey Thanks! Transferred and merged.

@blakeembrey blakeembrey deleted the issue-template branch February 5, 2020 02:05
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.

3 participants