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
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
-[ ] The code has been formatted properly using `go fmt ./...`.
4
4
-[ ] All [static analysis checks](https://github.com/jfrog/jfrog-cli-application/actions/workflows/analysis.yml) passed.
5
5
-[ ] All [tests](https://github.com/jfrog/jfrog-cli-application/actions/workflows/tests.yml) have passed. If this feature is not already covered by the tests, new tests have been added.
6
-
-[ ] All integration tests have passed locally as they cannot be automated yet.
7
-
-[ ] All changes are detailed at the description. if not already covered at [JFrog Documentation](https://github.com/jfrog/documentation), new documentation have been added.
6
+
-[ ] All [E2E tests](https://github.com/jfrog/jfrog-cli-application/actions/workflows/e2e-tests.yml) have passed.
During local development, if you come across code that needs to be modified in one of the mentioned modules, it is advisable to replace the dependency with a local clone of the module.
28
-
29
-
<details>
30
-
<summary>Replacing a dependency with a local clone</summary>
31
-
32
-
---
33
-
34
-
To include this local dependency, For instance, let's assume you wish to modify files from `jfrog-cli-core`, modify the `go.mod` file as follows:
Afterward, execute `go mod tidy` to ensure the Go module files are updated. Note that Go will automatically adjust the version in the `go.mod` file.
41
-
42
-
---
43
-
44
-
</details>
45
-
46
-
47
22
## 🚦 Running Tests
48
23
49
-
When running tests, builds and repositories with timestamps like `cli-rt1-1592990748` and `cli-rt2-1592990748` will be created. The content of these repositories will be deleted once the tests are completed.
50
-
51
-
To run tests, use the following command:
24
+
To run unit tests, use the following command:
52
25
53
26
```
54
-
go test -v github.com/jfrog/jfrog-cli-application [test-types] [flags]
Once you have completed your coding changes, it is recommended to push the modifications made to the other modules first. Once these changes are pushed, you can update this project to resolve dependencies from your GitHub fork or branch.
98
-
99
-
<details>
100
-
101
-
<summary>Resolve dependencies from GitHub fork or branch</summary>
102
-
103
-
---
104
-
105
-
To achieve this, modify the `go.mod` file to point the dependency to your repository and branch, as shown in the example below:
106
-
107
-
```
108
-
replace github.com/jfrog/jfrog-cli-core/v2 => github.com/jfrog/jfrog-cli-core/v2 dev
109
-
```
110
-
111
-
Finally, execute `go mod tidy` to update the Go module files. Please note that Go will automatically update the version in the `go.mod` file.
112
-
113
-
---
114
-
115
-
</details>
116
-
117
36
### Before submitting the pull request, ensure:
118
37
119
-
- Your changes are covered by `unit` and `integration` tests. If not, please add new tests.
120
-
- The documentation covers the changes, if not please add and make changes at [The documentation repository](https://github.com/jfrog/documentation)
121
-
-Run the go linter with --fix flag `golangci-lint run --fix`
38
+
- Your changes are covered by `unit` and `e2e` tests. If not, please add new tests.
39
+
- The code has been validated to compile successfully by running `go vet ./...`
40
+
-The code has been formatted properly using `go fmt ./...`
122
41
123
42
### When creating the pull request, ensure:
124
43
125
-
- The pull request is on the `dev` branch.
44
+
- The pull request is targeting the `main` branch.
126
45
- The pull request description describes the changes made.
0 commit comments