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: CONTRIBUTING.md
+17-5
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,14 @@ Using
8
8
git commit -s
9
9
```
10
10
11
-
to sign-off on commits is preferred, but not required. See https://developercertificate.org/ for more information.
11
+
to sign-off on commits is preferred, but not required. See
12
+
https://developercertificate.org/ for more information.
12
13
13
14
### Short Log Headers
14
15
15
-
To categorize commits and make release log generation easier, please use categorization headers on the first line of git commit messages. The headers the project uses are:
16
+
To categorize commits and make release log generation easier, please
17
+
use categorization headers on the first line of git commit messages.
18
+
The headers the project uses are:
16
19
17
20
| Prefix | Description |
18
21
| ------ | ----------- |
@@ -28,11 +31,16 @@ To categorize commits and make release log generation easier, please use categor
28
31
29
32
This list may expand over time.
30
33
31
-
NOTE: Short log messages without a header like this will be excluded from release announcements. That may be appropriate for some commits.
34
+
NOTE: Short log messages without a header like this will be excluded
35
+
from release announcements. That may be appropriate for some commits.
32
36
33
37
### Consolidated Project History
34
38
35
-
Sending pull requests is the preferred workflow, which means contributors need to track the upstream repo in their forked copies. Please avoid merge commits as you update your forks so that the commit history in the main project is consolidated. An easy way to do that is:
39
+
Sending pull requests is the preferred workflow, which means
40
+
contributors need to track the upstream repo in their forked copies.
41
+
Please avoid merge commits as you update your forks so that the commit
42
+
history in the main project is consolidated. An easy way to do that
43
+
is:
36
44
37
45
```sh
38
46
git checkout master
@@ -42,4 +50,8 @@ git rebase upstream/master
42
50
git push -f
43
51
```
44
52
45
-
This will track upstream and rebase your copy to the upstream copy. The force push is required to your copy since you are rewriting the project history to match upstream. You need to do this on a clean repo, so stash anything you are working on and ensure your copy is clean.
53
+
This will track upstream and rebase your copy to the upstream copy.
54
+
The force push is required to your copy since you are rewriting the
55
+
project history to match upstream. You need to do this on a clean
56
+
repo, so stash anything you are working on and ensure your copy is
In addition to the above test runs, rpminspect is built for Fedora Linux on these platforms:
50
50
51
-
| Platform | Status |
51
+
| Platform | Status |
52
52
|:-------------------|----:|
53
53
|[aarch64](https://en.wikipedia.org/wiki/AArch64)|[](https://github.com/rpminspect/rpminspect/actions/workflows/fedora-aarch64.yml)|
54
54
|[ppc64le](https://en.wikipedia.org/wiki/Ppc64)|[](https://github.com/rpminspect/rpminspect/actions/workflows/fedora-ppc64le.yml)|
0 commit comments