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.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Contributing to MindPoint Group Projects
1
+
Contributing to Ansible-Lockdown Projects
2
2
========================================
3
3
4
4
Rules
@@ -7,19 +7,20 @@ Rules
7
7
2) All commits must have Signed-off-by (Signed-off-by: Joan Doe <joan.doe@email.com>) in the commit message (details in Signing section)
8
8
3) All work is done in your own branch
9
9
4) All pull requests go into the devel branch. There are automated checks for signed commits, signoff in commit message, and functional testing)
10
-
5) Be open and nice to eachother
10
+
5) Be open and nice to each other
11
11
12
12
Workflow
13
13
--------
14
14
- Your work is done in your own individual branch. Make sure to to Signed-off and GPG sign all commits you intend to merge
15
15
- All community Pull Requests are into the devel branch. There are automated checks for GPG signed, Signed-off in commits, and functional tests before being approved. If your pull request comes in from outside of our repo, the pull request will go into a staging branch. There is info needed from our repo for our CI/CD testing.
16
16
- Once your changes are merged and a more detailed review is complete, an authorized member will merge your changes into the main branch for a new release
17
+
17
18
Signing your contribution
18
19
-------------------------
19
20
20
21
We've chosen to use the Developer's Certificate of Origin (DCO) method
21
22
that is employed by the Linux Kernel Project, which provides a simple
22
-
way to contribute to MindPoint Group projects.
23
+
way to contribute to Ansible-Lockdown projects.
23
24
24
25
The process is to certify the below DCO 1.1 text
25
26
::
@@ -60,7 +61,6 @@ following text in your contribution commit message:
60
61
61
62
::
62
63
63
-
64
64
This message can be entered manually, or if you have configured git
65
65
with the correct `user.name` and `user.email`, you can use the `-s`
66
66
option to `git commit` to automatically include the signoff message.
# This variable is a toggle for enabling/disabling the automated
872
+
# setting of an owner (specified in variable `rhel8cis_unowned_owner`)
873
+
# for all unowned files and directories.
874
+
# Possible values are `true` and `false`.
875
+
amazon2cis_ownership_adjust: true
876
+
amazon2cis_exclude_unowned_search_path: (! -path "/run/user/*" -a ! -path "/proc/*" -a ! -path "*/containerd/*" -a ! -path "*/kubelet/pods/*" -a ! -path "*/kubelet/plugins/*" -a ! -path "/sys/fs/cgroup/memory/*" -a ! -path "/var/*/private/*")
0 commit comments