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: README.md
+17-8Lines changed: 17 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,14 +15,6 @@ Template to quickly spin up a Go module project.
15
15
-`ci.yaml`: automatically run tests and generate code coverage report.
16
16
-`release.yaml`: automatically create a new release.
17
17
18
-
**Workflow**
19
-
20
-
Workflow implemented by this template is as follows:
21
-
22
-
- Dependencies are checked and updated weekly by `dependabot.yaml`, and then PRs are automatically merged to `main` branch by `automerge-dependabot.yaml`.
23
-
-`ci.yaml` is triggered on every push to any branch to run tests and generate code coverage report.
24
-
- Once PR is approved and merged to `release` branch, `release.yaml` is triggered to create a new release. Then a new PR is created to merge `release` branch to `main` branch.
25
-
26
18
## Usage
27
19
28
20
1. Create new project from this template:
@@ -35,6 +27,23 @@ Workflow implemented by this template is as follows:
35
27
5. Update other files to suit your needs.
36
28
6. Happy coding!
37
29
30
+
**Workflows**
31
+
32
+
Workflows implemented by this template are as the following:
33
+
34
+
- Dependencies are checked and updated weekly by `dependabot.yaml`, and then PRs are automatically merged to `main` branch by `automerge-dependabot.yaml`.
35
+
-`ci.yaml` is triggered on every push to any branch to run tests and generate code coverage report.
36
+
- Once PR is approved and merged to `release` branch, `release.yaml` is triggered to create a new release. Then a new PR is created to merge `release` branch to `main` branch.
37
+
38
+
A suggested git workflow to use with this template is as the following:
39
+
40
+
- Work on your code in development/feature branches as usual.
41
+
- Once ready, create a PR to merge your development/feature branch to `release` branch.
42
+
- Workflow `release.yaml` will be triggered to create a new release.
43
+
- Then a new PR will be created to merge `release` branch to `main` branch. Note: you have to review and approve the PR by yourself to finalize the merge.
44
+
45
+
> Remember to enable the setting "Allow GitHub Actions to create and approve pull requests" from project's `Settings -> Actions -> General`.
46
+
38
47
## License
39
48
40
49
This template is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details.
0 commit comments