Skip to content

Conversation

@susodapop
Copy link
Contributor

@susodapop susodapop commented Jul 1, 2022

Introduces Databricks standard DCO to the CONTRIBUTING guide.

Also adds a GitHub Action step which checks each commit in the pull request for a DCO sign-off and leaves a comment if this check fails.

One challenging aspect of this approach is that our current DCO check step doesn't have any outputs hooks that let us access its list of which commits failed the DCO check. I can write a custom action step that forks the existing behaviour and sets those outputs as a follow-up if it becomes necessary.

For now, any member of this org can see exactly which commits failed the DCO check by examining the PR Check results. These aren't visible to outside contributors, though, which is not as convenient.

Example comment:

CleanShot 2022-07-29 at 16 03 38@2x

Copy link
Contributor

@yunbodeng-db yunbodeng-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
The check itself comes from the DCO Check GitHub app. These apps are
tied directly to GitHub which is why the `app_id` is a known constant.
It's the same id regardless of the repository it monitors.

These were forked from MLFlow's public repository:

https: //github.com/mlflow/mlflow/blob/master/.github/workflows/notify-dco-failure.js
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
This reverts commit 16b438c.

We're going to use a GitHub Action for DCO checks instead of a GH App

Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
@github-actions
Copy link

Array

susodapop added 11 commits July 29, 2022 15:45
Intentionally not signing this commit to make sure the automated DCO check behaves as expected.

Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
This reverts commit 0a00449.

Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
@github-actions
Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide
every commit message must include a sign-off. You can retroactively apply this sign-off with an interactive rebase.

@github-actions
Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off. One or more of your commits is missing this sign-off message. You can retroactively apply this sign-off with an interactive rebase.

@github-actions
Copy link

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
Signed-off-by: Jesse Whitehouse <jesse@whitehouse.dev>
@yunbodeng-db
Copy link
Contributor

We need to do this to all other connectors as well?

@susodapop susodapop merged commit 2961524 into main Aug 1, 2022
@susodapop susodapop deleted the add-cla branch August 1, 2022 16:14
@susodapop
Copy link
Contributor Author

Yes I've created tracking tickets internally to implement this for NodeJS and Go.

moderakh pushed a commit to moderakh/databricks-sql-python that referenced this pull request Aug 24, 2022
Includes a GitHub Action which checks for a valid sign-off on every proposed commit

Signed-off-by: Moe Derakhshani <moe.derakhshani@databricks.com>
saishreeeee pushed a commit that referenced this pull request Jun 4, 2025
Includes a GitHub Action which checks for a valid sign-off on every proposed commit
saishreeeee pushed a commit that referenced this pull request Jun 4, 2025
Includes a GitHub Action which checks for a valid sign-off on every proposed commit

Signed-off-by: Sai Shree Pradhan <saishree.pradhan@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants