Skip to content

Commit

Permalink
Update DCO instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
robert-zaremba committed Nov 27, 2024
1 parent b8fd6ba commit 7980043
Showing 1 changed file with 15 additions and 4 deletions.
19 changes: 15 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,19 @@ This repository contains shared resources about contribution and security polici

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. See the [full text of the DCO](DCO.txt).

Check failure on line 13 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Line length

README.md:13:81 MD013/line-length Line length [Expected: 80; Actual: 232] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md013.md

**We require all contributors** to affirm [Developer Certificate of Origin](https://developercertificate.org/) (DCO) on Pull Requests. It requires all commit messages to contain the Signed-off-by line with an email address that matches the commit author. You can accomplish this by either:
**We require all contributors** to affirm [Developer Certificate of Origin](https://developercertificate.org/) (DCO) on Pull Requests. It requires:

Check failure on line 15 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Line length

README.md:15:81 MD013/line-length Line length [Expected: 80; Actual: 147] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md013.md

- Set `commit.gpgsign = true` in your `.gitconfig`. The easiest way is to set it globally: `git config --global commit.gpgsign true`.
- add `-S` option when running `git` command, eg: `git commit -S -m "YOUR_COMMIT_MESSAGE"`
- [Adding signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) to your GitHub, for commits done through GitHub.

Check failure on line 17 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Multiple consecutive blank lines

README.md:17 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md012.md
1. all commit messages to contain the Signed-off-by line with an email address that matches the commit author: `Signed-off-by: Author Name <authoremail@example.com>`. You can also do this automatically by using the -s flag (i.e., `git commit -s`).

Check failure on line 18 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Line length

README.md:18:81 MD013/line-length Line length [Expected: 80; Actual: 247] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md013.md
- To add your Signed-off-by line to every commit in your branch you can run

Check failure on line 20 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Trailing spaces

README.md:20:1 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 4] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md009.md
```

Check failure on line 21 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Fenced code blocks should have a language specified

README.md:21 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md040.md
git rebase HEAD~<number of commits in your branch> --signoff
git push --force-with-lease
```

Check failure on line 25 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Trailing spaces

README.md:25:1 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 8] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md009.md
2. Sign all your commits. You can accomplish this by:
- Set `commit.gpgsign = true` in your `.gitconfig`. The easiest way is to set it globally: `git config --global commit.gpgsign true`.

Check failure on line 28 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Line length

README.md:28:81 MD013/line-length Line length [Expected: 80; Actual: 137] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md013.md
- add `-S` option when running `git` command, eg: `git commit -S -m "YOUR_COMMIT_MESSAGE"`
- [Adding signing key](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) to your GitHub, for commits done through GitHub.

Check failure on line 30 in README.md

View workflow job for this annotation

GitHub Actions / markdown-lint

Line length

README.md:30:81 MD013/line-length Line length [Expected: 80; Actual: 173] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md013.md

0 comments on commit 7980043

Please sign in to comment.