-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
Internal ToolingIssues related to our tooling and monorepo infrastructoreIssues related to our tooling and monorepo infrastructore
Description
Description / Steps to reproduce / Feature proposal
We're switching to use Developer Certificate of Origin (DCO) for loopback-next
repo, after switched it for the loopback4-example-shopping
and loopback.io-search
repos.
Acceptance Criteria
- Look into how to configure git to automatically sign
- Investigate to see if we can use
husky
to check the sign-off, so that it will fail right away without signing instead of waiting for CI to fail. - Enable DCO for
loopback-next
- Can be done through https://github.com/integration/dco. Might need admin rights in order to configure it on
loopback-next
repo
- Can be done through https://github.com/integration/dco. Might need admin rights in order to configure it on
- Update the "contribute code" docs: https://loopback.io/doc/en/contrib/code-contrib-lb4.html
- Update README or contribute section in the repo, similar to https://github.com/strongloop/loopback4-example-shopping#contributing
- Make sure the DCO process is compatible with CI (for future consideration when we have a special functional id to make releases).
Reference
- This CONTRIBUTING.md contains more info on how to sign and fix commit message if you miss the signing: https://github.com/strongloop/loopback.io-search/blob/master/CONTRIBUTING.md
- @bajtos also mentioned there's a way to configure git to automatically sign. Might want to include that instruction too.
Metadata
Metadata
Assignees
Labels
Internal ToolingIssues related to our tooling and monorepo infrastructoreIssues related to our tooling and monorepo infrastructore