cla-assistant / cla-assistant

Contributor License Agreement assistant (CLA assistant)

Home Page:https://cla-assistant.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

General Troubleshooting

michael-spengler opened this issue · comments

Provide a diagram for typical symptoms and solutions.

Roles
Contributor
Admin

Typical example symptoms & solutions:

  1. Contributor can not sign CLA --> check this link to see how to configure git: git config ...
  2. CLA Status seems wrong --> Contributor should retrigger the CLA check vie "Recheck" Button or via API
commented

Here is a collection of responses from previous issues:

CLA Assistant checks the committers of the PR, whether they have signed the CLA or not. In your PR you have used an invalid email address, so GitHub can't recognise you as a committer and CLA Assistant won't change the status to green.

CLA assistant checks whether all committers of a PR have signed the CLA or not. In this case you (@ ...) are the author of the PR but not a committer

Probably you have used another e-mail address in git config as the one stored in your GitHub account. Please add the e-mail address to your account

The trickiest part with whitelisting bots is to get their right login name. I usually look into the api response by converting PR url zio/zio#3183 to a get API url "https://api.github.com/repos/zio/zio/pulls/3183/commits"
There you can see the login name of the committer "committer": { "login": "scala-steward",
If you change the name from scala-steward[bot] to scala-steward then it should work well.

most common issues and solutions flow chart


CLA-Issue-tracking-flow-chart

Link 1
Link 2
Link 3
Link 4

If the above issue tracking flow chart helps in solving your issue then please kindly give 👍 reaction to this comment. We will try to automate our technical support as much as possible for all the commonly occurring issues, FAQ :)

commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

commented

We're having an odd issue with our self-hosted CLA assistant here: https://cla.skybasedb.com. Like you can see, the styles.css never loads and fails with a 'MIME type error' (reading off a chrome inspection tab). FWIW, we're running cla-assistant off the v2.8.5 tag

Update
Turns out that it was an issue with nginx

commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.