-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add configuration for CLA Assistant GitHub Action #15
Merged
Merged
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
3a6d8e5
Add configuration for CLA Assistant GitHub Action
michaelosthege 0504a15
Add adapted CLA from R-R and customize assistant
michaelosthege a12fae8
Don't run CLA on issue comments
michaelosthege f531a20
Apply fixes to the action YML
michaelosthege 1161bd3
Fix typo in comment template
michaelosthege 1939885
Fix another typo in the comment template
michaelosthege File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
name: "CLA Assistant" | ||
on: | ||
pull_request_target: | ||
types: [opened,closed,synchronize] | ||
|
||
# explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings | ||
permissions: | ||
actions: write | ||
contents: write | ||
pull-requests: write | ||
statuses: write | ||
|
||
jobs: | ||
CLAAssistant: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: "CLA Assistant" | ||
if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target' | ||
uses: contributor-assistant/[email protected] | ||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
# The below token has repo scope for the project configured further below to store signatures. | ||
PERSONAL_ACCESS_TOKEN: ${{ secrets.JUBIOTECH_CLA_SIGNATURES }} | ||
PATH_TO_CLA: 'https://github.com/jubiotech/detl/blob/main/CLA.md' | ||
with: | ||
path-to-signatures: 'signatures_detl.json' | ||
path-to-document: $PATH_TO_CLA | ||
# branch should not be protected | ||
branch: 'main' | ||
allowlist: dependabot[bot] | ||
|
||
# the followings are the optional inputs - If the optional inputs are not given, then default values will be taken | ||
# 👇 the remote organization and repo where the signatures should be stored | ||
remote-organization-name: jubiotech | ||
remote-repository-name: cla-signatures | ||
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures' | ||
#signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo' | ||
custom-notsigned-prcomment: > | ||
Thank you for your submission, we really appreciate it! | ||
|
||
Like many open-source projects we ask that you sign our [Contributor License Agreement](${{ env.PATH_TO_CLA }}) before we can accept your contribution. | ||
To sign, please post two separate comments based on the following templates 👇 | ||
|
||
1. Comment: | ||
|
||
---- | ||
|
||
\- [ ] The JuBiotech maintainers know my real name. | ||
|
||
At least one of the following two applies: | ||
|
||
\- [ ] The JuBiotech maintainers know my current employer. | ||
|
||
\- [ ] I am making not making this contribution on behalf of my current employer. | ||
|
||
|
||
---- | ||
|
||
2. Comment: | ||
custom-pr-sign-comment: > | ||
I have read the CLA Document and I hereby sign the CLA. | ||
#custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.' | ||
# 👇 prevent contributors from revoking signatures after the merge (this is also the default) | ||
lock-pullrequest-aftermerge: true | ||
#use-dco-flag: true - If you are using DCO instead of CLA |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
# `detl` CLA | ||
|
||
Thank you for your interest in contributing to Forschungszentrum Jülich GmbH - Institute for Bio- and Geosciences: IBG-1's `detl` project ("We" or "Us"). | ||
|
||
The purpose of this contributor agreement is to clarify and document the rights granted by contributors to Us. | ||
To make this document effective, please follow the instructions below. | ||
|
||
# How to use this CLA | ||
|
||
If You are an employee and have created the Contribution as part of your employment, You need to have Your employers approval as a Legal Entity. | ||
If You do not own the Copyright in the entire work of authorship, any other author of the Contribution must also sign this. | ||
|
||
# Definitions | ||
|
||
**"You"** means the individual Copyright owner who Submits a Contribution to Us. | ||
|
||
**"Legal Entity"** means an entity that is not a natural person. | ||
|
||
**"Contribution"** means any original work of authorship, including any original modifications or additions to an existing work of authorship, Submitted by You to Us, in which You own the Copyright. | ||
|
||
**"Copyright"** means all rights protecting works of authorship, including copyright, moral and neighboring rights, as appropriate, for the full term of their existence. | ||
|
||
**"Material"** means the software or documentation made available by Us to third parties. | ||
When this Agreement covers more than one software project, the Material means the software or documentation to which the Contribution was Submitted. | ||
After You Submit the Contribution, it may be included in the Material. | ||
|
||
**"Submit"** means any act by which a Contribution is transferred to Us by You by means of tangible or intangible media, including but not limited to electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Us, but excluding any transfer that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution." | ||
|
||
**"Documentation"** means any non-software portion of a Contribution. | ||
|
||
# Rights and Obligations | ||
|
||
You hereby grant to Us a worldwide, royalty-free, non-exclusive, perpetual and irrevocable license, with the right to transfer an unlimited number of licenses or to grant sublicenses to third parties, under the Copyright covering the Contribution to use the Contribution by all means. | ||
|
||
We agree to (sub)license the Contribution or any Materials containing it, based on or derived from your Contribution non-exclusively under the terms of any licenses the Free Software Foundation classifies as Free Software License and which are approved by the Open Source Initiative as Open Source licenses. | ||
|
||
# Copyright | ||
|
||
You warrant, that you are legitimated to license the Contribution to us. | ||
|
||
# Acceptance of the CLA | ||
|
||
By submitting your Contribution via the [Repository](https://github.com/jubiotech/detl) you accept this agreement. | ||
|
||
|
||
# Liability | ||
|
||
Except in cases of willful misconduct or physical damage directly caused to natural persons, the Parties will not be liable for any direct or indirect, material or moral, damages of any kind, arising out of the Licence or of the use of the Material, including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, loss of data or any commercial damage. | ||
However, the Licensor will be liable under statutory product liability laws as far such laws apply to the Material. | ||
|
||
# Warranty | ||
|
||
The Material is a work in progress, which is continuously being improved by numerous Contributors. | ||
It is not a finished work and may therefore contain defects or "bugs" inherent to this type of development. | ||
|
||
For the above reason, the Material is provided on an "as is" basis and without warranties of any kind concerning the Material, including without limitation, | ||
merchantability, fitness for a particular purpose, absence of defects or errors, accuracy, non-infringement of intellectual property rights other than copyright. | ||
|
||
# Miscellaneous | ||
|
||
This Agreement and all disputes, claims, actions, suits or other proceedings arising out of this agreement or relating in any way to it shall be governed by the laws of Germany excluding its private international law provisions. | ||
|
||
If any provision of this Agreement is found void and unenforceable, such provision will be replaced to the extent possible with a provision that comes closest to the meaning of the original provision and that is enforceable. | ||
The terms and conditions set forth in this Agreement shall apply notwithstanding any failure of essential purpose of this Agreement or any limited remedy to the maximum extent possible under law. | ||
|
||
You agree to notify Us of any facts or circumstances of which You become aware that would make this Agreement inaccurate in any respect. |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldnt this be
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, if the contribution is made in the contributors free time, their current employer is irrelevant. They might also be self- or unemployed. Therefore only one of the two task items must apply.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get that, I just think there is one making too many in the second point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah of course, sorry my in-mind-diffing was incomplete
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really think we need to consult Alexander Storm here. In my view, it makes a difference if somehone has an employer of if he/she made the contribution during working hours. To make things more complex, contributions in "free time" might still require permission of thge employer (or not). This is not our business but it must be clear to the contributor which option to choose. Some contributors (like Sam) have multiple accounts to clarify on/off work contributions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, then I will summarize the proposed procedure, texts & mockup screenshots, and consult him by email (cc y'all).