Add CLA troubleshooting guide for inconsistent bot reports

[Copilot]

Maintainers lack visibility into CLA status and investigation procedures when the CLA bot reports inconsistent states across PRs from the same contributor.

Changes

• Created cla-troubleshooting-guide.md

  • Investigation workflow: verify commit emails, check bot comments, verify signature status
  • Escalation paths to support team with Microsoft CLA database access
  • Common solutions: re-trigger bot, verify email configuration, re-sign CLA
  • Technical details on bot behavior and known limitations

• Updated readme.md

  • Added CLA support to services list
  • New "Common Support Scenarios" section with direct link to guide

• Updated new-projects.md

  • Referenced troubleshooting guide after CLA signing section
  • Enhanced "Configure CLA bot" task description

Example Usage

When encountering inconsistent reports:

# Step 1: Check commit emails across PRs
git log --format="%H %ae %an" origin/pull/2251/head
git log --format="%H %ae %an" origin/pull/2258/head

# Step 2: Compare emails and escalate via support request template
# Link provided: github.com/dotnet-foundation/projects/issues/new?template=project-support-request.yml

Maintainers can now self-investigate common issues before escalating to @ChrisSfanos and the support team.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Project Support]: Rx.NET - inconsistent CLA bot reports</issue_title>
<issue_description>### Project

Rx.NET (Reactive Extensions for .NET)

Project Url

https://github.com/dotnet/reactive

Description

One person has submitted two PRs, and GitHub is saying for one of them that the person has agreed to the CLA, and in the other that they have not!

dotnet/reactive#2251
dotnet/reactive#2258

I don't know how to investigate CLA status—I've always just relied on the automation in GitHub doing the right thing. Can I find out whether this person has indeed agreed to the CLA, and if so, can we get the 2nd PR unstuck, as I'd like to merge it.

Due By

2025/12/1</issue_description>

<agent_instructions>create a plan and determine how we would investigate these reports</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@glennawatson The CLA bot is run by Microsoft internal I believe, so likely will be a @ChrisSfanos job to check it out.

• Fixes [Project Support]: Rx.NET - inconsistent CLA bot reports #476

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.