You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- Check at least one. If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->
7
-
8
-
-[ ] Bugfix
9
-
-[ ] Feature
10
-
-[ ] Docs
11
-
-[ ] New Binding issue #___
12
-
-[ ] Code style update
13
-
-[ ] Refactor
14
-
-[ ] Build-related changes
15
-
-[ ] Other, please describe:
2
+
<!-- Delete ones that doesnt apply-->
3
+
4
+
- Bugfix - fixes issues- give issue github url/details here.
5
+
- Feature
6
+
- Docs
7
+
- Code style update
8
+
- Refactor
9
+
- Build-related changes
10
+
- Other, please describe:
11
+
12
+
### Screenshots or Gifs of the change
13
+
1. Any visual or workflow changes must come with a gif or screenshot.
14
+
2. Gif screen recordings help more if present. You can use one of the below free screen recorders:
15
+
1. windows gif recorder- https://www.screentogif.com/
16
+
2. mac gif recorder- https://apps.apple.com/au/app/giphy-capture-the-gif-maker/id668208984?mt=12
17
+
3. linux gif recorder- https://github.com/phw/peek
16
18
17
19
### Does this PR introduce a breaking change?
18
20
<!-- If yes, please describe the impact and migration path for existing applications in an attached issue. -->
19
21
20
-
-[ ] Yes, and the changes were approved in issue #___
21
-
-[ ] No
22
+
- Yes, and the changes were approved in issue #___
23
+
- No
24
+
25
+
### Tests done
26
+
- Describe unit tests done
27
+
- Describe integration tests done
28
+
- Describe manual tests done
22
29
23
30
### Checklist
24
-
-[ ] When resolving issues, they are referenced in the PR's title (e.g `fix: remove a typo, closes #___, #___`)
25
-
-[ ]A change file is added if any packages will require a version bump due to this PR per [the instructions in the readme](https://github.com/tauri-apps/tauri/blob/dev/.changes/readme.md).
26
-
-[ ] I have added a convincing reason for adding this feature, if necessary
31
+
-[ ] When resolving issues, reference those issue URLs in description.
32
+
-[ ]Propose a changelog if this pull request has any customer facing impact.
33
+
-[ ] I have added a convincing reason for adding this feature, if necessary.
27
34
28
35
### Other information
29
36
@@ -32,3 +39,4 @@ Update "[ ]" to "[x]" to check a box
32
39
* It's OK to have multiple small commits as you work on the PR - we will let GitHub automatically squash it before merging.
33
40
* If adding new feature:, Provide convincing reason to add this feature. Ideally you should open a suggestion issue first and have it greenlighted before working on it.
34
41
* If fixing a bug:Provide detailed description of the bug in the PR, or link to an issue that does.
42
+
* Provide screenshots or gifs of the changes whenever possible.
0 commit comments