CI: require DCO sign-off
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Require a DCO sign-off on commits, matching Nextcloud convention across the org.
Contributors sign off with:
git commit -s -m "your message"
The README already documents this; nothing enforces it.
Scope
Add the DCO check the rest of the org uses, so unsigned commits fail the PR rather than being caught by a human.
Part of #38.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing CI configuration and the README's DCO sign-off instructions, then compare the DCO check used elsewhere in the Nextcloud organization. Add enforcement so a pull request with an unsigned commit fails, and verify the check distinguishes signed from unsigned commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100