Skip to content

/cla-assistant

Contributor License Agreement assistant (CLA assistant)
  1. JavaScript 84.3%
  2. HTML 11.1%
  3. CSS 4.5%
  4. Shell 0.1%
JavaScript HTML CSS Shell
Find file
Download ZIP
Latest commit 55ebec0 @KharitonOff KharitonOff Merge pull request #110 from laughinghan/friendlier-PR-comment 
Friendlier PR comment, helps with #105
Failed to load latest commit information.
src Reword PR comment at @casche and @dfarr's suggestion
.bowerrc initial upload
.cf.sh initial upload
.cfignore added rotating logging for bunyan
.codeclimate.yml Merge branch 'master' of github.com:cla-assistant/cla-assistant
.env.example Update setup info in readme, related to #26, #21
.eslintignore uglify js files
.eslintrc clean up eslint warnings
.gitignore update dependencies
.travis.yml switch to new travis infrastructure
DESCRIPTION.MD Remove apostrophe from plural for CLAs
Gruntfile.js clean up my-cla
LICENSE update on License; some gist info screen improvements
README.md add codeclimate badge
app.js initial upload
bower.json uglify js files
cla-assistant.json load default cla url from json file; close #44
package.json update dependencies

README.md

CLA assistant Build Status Dependency Status devDependency Status Coverage Status Code Climate ReviewNinja

Contributor License Agreement assistant

Streamline your workflow and let CLA assistant handle the legal side of contributions to a repository for you. CLA assistant enables contributors to sign CLAs from within a pull request.

To get started, simply store your CLA as a GitHub Gist file then link it with the repository in CLA assistant. Then sit back and relax while CLA assistant:

  • Comments on each opened pull request to ask the contributor to sign the CLA
  • Allows contributors to sign a CLA from within a pull request
  • Authenticates the signee with his or her GitHub account
  • Updates the status of a pull request when the contributor agrees to the CLA
  • Automatically asks users to re-sign the CLA for each new pull request in the event the associated Gist & CLA has changed

Repository owners can review a list of users who signed the CLA for each version of it. To get started, visit https://cla-assistant.io.

Try

CLA assistant is provided by SAP as a free hosted offering under: https://cla-assistant.io/. Please leave us a GitHub issue if you have feedback.

For SAP open source projects please use the SAP Individual Contributor License Agreement.

FAQ

Where is the list of signees stored?

We store all the data in a MongoDB hosted by mongolab.

Where can I see the list of signees? Is there a way to import/export the signee data?

You can see the list of signees on the user interface. There is also a possibility for you to export the list as a .csv file.

Who can I contact for help?

In case of problems or any further questions, please open an issue in GitHub. We always appreciate helpful tips and support for the project.

Setup your own instance of CLA assistant

Clone this repository, change into the cloned directory and install dependencies.

git clone git@github.com:cla-assistant/cla-assistant.git
cd ./cla-assistant
npm install

Register an application on GitHub. The callback URL needs to be of the form

<PROTOCOL>://<HOST>:<PORT>/auth/github/callback.

Copy the sample configuration file .env.example file to .env.

cp .env.example .env

The following are the environment variables you have to configure to run a private instance:

  • HOST: This should only set the hostname of your CLA assistant instance (without the protocol).
  • PORT: The local port to bind to. Defaults to 5000.
  • PROTOCOL: Valid options are "http" or "https".
  • GITHUB_CLIENT: From your registered application in GitHub.
  • GITHUB_SECRET: From your registered application in GitHub.
  • GITHUB_USER: For CLA assistant to comment on pull requests, it requires a GitHub account.
  • GITHUB_PASS: To access the GitHub account to comment on pull requests, CLA assistant needs an API Token. It can be generated here https://github.com/settings/tokens/new. The Only scope required is repo_public.
  • MONGODB: This has to be in form of a mongodb url, e.g. mongodb://<user>:<password>@<host>:<port>/<dbname>.
  • SLACK_URL: Optional. You can use it in case you would like to get log-notifications posted in your slack chat.
  • SLACK_TOKEN: Optional.

Hint: For further reading on setting up MongoDB, go to http://docs.mongodb.org/manual/tutorial/getting-started/ http://docs.mongodb.org/manual/reference/method/db.createUser

Run grunt in order to build the application.

./node_modules/grunt-cli/bin/grunt build

During development, just run the grunt default task to build the app, start linter checks and run unit tests on each change of relevant .js files.

./node_modules/grunt-cli/bin/grunt

Finally, source the environment file and start the application.

source .env
npm start

License

Contributor License Agreement assistant

Copyright (c) 2014 SAP SE or an SAP affiliate company. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Credits

SAP

:heart: from the GitHub team @ SAP

Something went wrong with that request. Please try again.