Use different DCO action implementation #210
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Switching from <https://github.com/tim-actions/dco> to <https://github.com/tisonkun/actions-dco>. While both implementations look very similar there are some differences: - The later implementation does not require use of additional action to pull PR commits because it does not rely on `commits` being setup in `core` context. - The later implementation is explicit about its LICENSE (AL2). Signed-off-by: Lukáš Vlček <lukas.vlcek@aiven.io>
This was referenced Aug 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switching from https://github.com/tim-actions/dco to https://github.com/tisonkun/actions-dco. While both implementations look very similar there are some differences:
commitsbeing setup incorecontext.Description
Describe your PR and add links to relevant issues.
DCO stands for Developer Certificate of Origin and it is your declaration that your contribution is correctly attributed and licensed. Please read more about how to attach DCO to your commits here (spoiler alert: in most cases it is as simple as using
-soption when doinggit commit).Please be aware that commits without DCO will cause failure of PR CI workflow and can not be merged.