File tree 4 files changed +6
-6
lines changed
4 files changed +6
-6
lines changed Original file line number Diff line number Diff line change @@ -3,9 +3,9 @@ name: Containers
3
3
4
4
on :
5
5
push :
6
- branches : [master ]
6
+ branches : [main ]
7
7
pull_request :
8
- branches : [master ]
8
+ branches : [main ]
9
9
10
10
env :
11
11
GO_TOOLCHAIN : " 1.15"
Original file line number Diff line number Diff line change 2
2
name : Go
3
3
on :
4
4
push :
5
- branches : [master ]
5
+ branches : [main ]
6
6
pull_request :
7
- branches : [master ]
7
+ branches : [main ]
8
8
9
9
env :
10
10
# Minimum supported Go toolchain
Original file line number Diff line number Diff line change @@ -31,7 +31,7 @@ are very busy and read the mailing lists.
31
31
32
32
This is a rough outline of what a contributor's workflow looks like:
33
33
34
- - Create a topic branch from where you want to base your work (usually master ).
34
+ - Create a topic branch from where you want to base your work (usually main ).
35
35
- Make commits of logical units.
36
36
- Make sure your commit messages are in the proper format (see below).
37
37
- Push your changes to a topic branch in your fork of the repository.
Original file line number Diff line number Diff line change @@ -19,7 +19,7 @@ Go bindings to systemd. The project has several packages:
19
19
20
20
An example HTTP server using socket activation can be quickly set up by following this README on a Linux machine running systemd:
21
21
22
- https://github.com/coreos/go-systemd/tree/master /examples/activation/httpserver
22
+ https://github.com/coreos/go-systemd/tree/main /examples/activation/httpserver
23
23
24
24
## systemd Service Notification
25
25
You can’t perform that action at this time.
0 commit comments