microsoft / contributorlicenseagreement Goto Github PK

Hello, I have a contributor who signed the CLA according to the bot's prompt:

@microsoft-github-policy-service agree [company="{your company}"]

Their reply included the brackets:

@microsoft-github-policy-service agree [company="self"]

My initial impression of the prompt was also taken literally - it wasn't immediately clear to me that this was syntactic and the brackets were to indicate the optional clause. Perhaps the prompt might include the examples as shown in the readme:

If you are contributing on behalf of yourself:
@microsoft-github-policy-service agree

If you are contributing on behalf of a company:
@microsoft-github-policy-service agree company="your company"

I've seen that the repository is listed as MIT license, but checking files headers I've seen they mention "the Microsoft License".

Which one is the right one?

Hi Team, Please take a look at that PR Azure/azure-kusto-java#272 . Though I have commented in the PR @microsoft-github-policy-service agree company="Microsoft", the CLA verification bot doesn't run.

Hey folks, I'm trying to add this to the jank-lang org and I have the initial PR adding the cla.yml here: jank-lang/.github#1

Unfortunately, even with the platformcontext.yml and the Policy Service installed, I'm not seeing an initial comment from the bot. Am I missing something?

The link on https://github.com/apps/microsoft-github-policy-service points to https://github.com/microsoft/GitOps which doesn't exist. Maybe a redirect and/or a new link is needed?

We would like to automate adding and removing labels on PRs when the bot informs the author about signing requirements. We can do this on the initial report since a comment is posted by the bot, but once the user "signs" the CLA there is no confirmation that the CLA was signed. If we had a message from the bot indicating the PR author has successfully signed the CLA then we could automate removing the label ourselves.

Our intern followed the CLA bot's instructions for his PR (microsoft/azure-pipelines-agent#3944) but the license requirement is still blocking the PR. Please let me know if I missed something.

See pythonnet/.github#1

According to README in ContributorLicenseAgreement

Create a seperate PR for this, the policy service will create a comment example bellow.

Policy service is not creating a comment under that PR.

I made my first contribution to a project which is supported by .NET Foundation: https://github.com/nunit/docfx-action. This is my first contribution: nunit/docfx-action#32. However, when I checked the pull request status, I saw that it said:

Contributor License Agreement is not agreed yet.
This check verifies that the author has agreed to a CLA with Microsoft.

I searched Google on how to sign a CLA, but I found nothing, so it looks impossible to sign a CLA. Can anybody point me to how to sign a CLA?

Good morning,

Two PRs on our repo are blocked on the CLA bot, even though the contributor has followed instructions:

microsoft/CCF#4563
microsoft/CCF#4563 (comment)

microsoft/CCF#4641
microsoft/CCF#4641 (comment)

The bot seems to be stuck:

I am not sure this is the right place to report this issue, but I found nowhere else, and I was encouraged by the existence of past issues, such as #80 and #77. Any help would be much appreciated!

Hi team,

My PR is stuck by license check Azure/azure-powershell#20341
Anyway to run the recheck?
Thanks

Same symptoms as previous issues i see listed as now closed.
See this PR if you need an example: microsoft/mu_basecore#147

Is there something that changed that needs to be updated. We have 20+ OSS repos that use this bot.

Thanks

Recently, we found the cla has some updates. The previous cls check is generate from microsoft-cla, but recently the task was generated by microsoft-github-policy-service.

Our PRs in Azure/azure-rest-api-specs repo has been blocked by cla. Here is the error message Required status check "license/cla" was not set by the expected GitHub app.

PR link: Azure/azure-rest-api-specs#21073

Could you take a look this isusse?

microsoft/CLRInstrumentationEngine#524

On invalid command, the CLA bot responds quickly with corrected commands. But on valid command, nothing happens and the
license/cla requirement is blocking the PR. Can someone take a look and/or provide guidance?

Hi guys,

We are trying to enable the policy, so I added the files from the readme to the repo: telerik/UI-For-UWP#522
Please add our org to the allowed external orgs list.

Thanks,
Kalin
Telerik

I am not able to agree to CLA. I did write a comment to @microsoft-github-policy-service agree company="microsoft" which is not successful.

PR link : Azure/azure-rest-api-specs#21128
Can someone help in unblocking this ??

We're seeing something similar to what others have reported here, with the bot not responding to the agreement message in Azure/azure-functions-tooling-feed#414

Can you please assist?

/ @ejizba

In microsoft/torchgeo#1908, the bot posted the same comment 3 times (I hid them because they were too long). Seems like a bug to me.

Like this one: OrchardCMS/OrchardCore#15036. The bot won't be able to accept the CLA. I'd argue, but IANAL, that it needn't either, and we can just merge the PR. Can you help, please?

test

The comments that the bot posts on PRs are very long and detailed. This is helpful before it's signed, but verbose afterwards. I wonder if it's possible to automatically hide the comments being made on a PR after the CLA is signed.

I am not able to agree to CLA. All attempts to write a comment to "@microsoft-github-policy-service" are not successful. For example:

This is the PR which is blocked: Azure/az-hop#1140

I get no reply from the bot to this command: @microsoft-github-policy-service agree company="Microsoft"

Any time the CLA bot fails to run on a PR (for various reasons), contributors and maintainers have to remember the best way to force the bot to rerun itself. A @microsoft-github-policy-service rerun command or something similar would be very useful. Simply tagging @microsoft-github-policy-service or issuing @microsoft-github-policy-service help could even yield a comment that talks about when rerun is needed and how to use it.

Closing and reopening the PR is our go-to stop-gap, but that is an annoying step to have to take, especially when there are PR checks that take hours to run and we want to avoid stopping or rerunning them.

Github recently added a new feature for merging pull requests called Merge Queues. Unfortunately, when we tried to turn this on the CLA workflow doesn't appear to get triggered when a pull request gets added to the merge queue which prevents the PR from being merged (required check). I'm wondering if this is on your radar to support this new feature or if you have any suggestions for getting this to run?

The bot is not running the CLA checks on the PR and is blocking PR merge.

ref:
Azure/azure-workload-identity#1008
Azure/azure-workload-identity#999

Greetings,

We are trying to get this PR approved: Azure/missionlz#761
It keeps getting stuck on the Licensing/CLA requirements and even though the author has input the correct information to sign the CLA it is not being approved. Please advise.

Thanks!

https://cla.opensource.microsoft.com/Azure/azure-rest-api-specs?pullRequest=20969

When I open above URL to sign CLA, I get the below error

Need to sign CLA for PR - Azure/azure-rest-api-specs#20969

The rerun command is great to have as an option; right now it only supports the PR author, which may be a bit unfamiliar to any early contributors to a project.

Would it be possible to have this expanded to support this command coming from anyone with write access or more to the repository, or at least admins, so that the project maintainers also have the option of kicking the CLA?

[Related to https://github.com//issues/123]

Could not get back a status from a PR even after several pushes.

microsoft/mu_rust_hid#3

Appears similar to issues our team has filed in the past like this one #72.

The bot is not running the CLA checks on the PR and is blocking PR merge.

ref:
Azure/azure-workload-identity#712