Skip to content

Commit 96b4aa1

Browse files
committed
Template cleanup
1 parent 7ef0e93 commit 96b4aa1

File tree

4 files changed

+9
-68
lines changed

4 files changed

+9
-68
lines changed

.github/template-cleanup.sh

Lines changed: 0 additions & 12 deletions
This file was deleted.

.github/template-cleanup/README.md

Lines changed: 0 additions & 13 deletions
This file was deleted.

.github/workflows/cleanup.yml

Lines changed: 0 additions & 33 deletions
This file was deleted.

README.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
1-
# React Native Reproducer
1+
# promise-reproducer
22

3-
This is the React Native **reproducer** template.
3+
![Build](https://github.com/philIip/promise-reproducer/workflows/Pre%20Merge%20Checks/badge.svg)
44

5-
You can use this template to create a minimal, complete, and reproducible project that the community can use to understand what's your problem. You can read more about the principles of a good reproducible project [here](https://stackoverflow.com/help/mcve).
5+
This is your new React Native Reproducer project.
66

7-
This template is up to date with `react-native@latest` as you can find it on [npm](https://www.npmjs.com/package/react-native/v/latest).
7+
## Reproducer todo list
88

9-
## How to use this repository
10-
11-
1. Click on [![Use this template](https://img.shields.io/badge/-Use%20this%20template-brightgreen)](https://github.com/cortinico/reproducer-react-native/generate) button to create a new repository starting from this one.
12-
2. Git clone your repository locally.
13-
3. Edit the project to reproduce the failure you're seeing.
14-
4. Push your changes, so that Github Actions can run the CI.
9+
- [x] Create a new reproducer project.
10+
- [ ] Git clone your repository locally.
11+
- [ ] Edit the project to reproduce the failure you're seeing.
12+
- [ ] Push your changes, so that Github Actions can run the CI.
13+
- [ ] Make sure the repository is public and share the link with the issue you reported.

0 commit comments

Comments
 (0)