Fix GitHub Copilot CLA allowlist to prevent false CLA requirement - #31
Conversation
|
@m7pr 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
Co-authored-by: m7pr <133694481+m7pr@users.noreply.github.com>
|
I have read the CLA Document and I hereby sign the CLA 1 out of 2 committers have signed the CLA. |
Signed-off-by: Marcin <133694481+m7pr@users.noreply.github.com>
|
I have read the CLA Document and I hereby sign the CLA |
This PR fixes an issue where GitHub Copilot was incorrectly being required to sign the CLA despite being added to the allowlist.
Problem
The CLA workflow had
copilotin the allowlist, but GitHub Copilot appears with different username formats when making contributions (such asgithub-copilot[bot]orcopilot[bot]). This caused the CLA Assistant to incorrectly flag Copilot contributions as requiring CLA signature, as shown in the issue screenshot where@copilotwas marked with a red X and required to sign the CLA.Solution
Updated the CLA workflow allowlist to include the correct GitHub Copilot bot formats:
github-copilot[bot](most common GitHub Copilot format)copilot[bot](alternative GitHub Copilot format)copilotentry for backward compatibilityThe allowlist now properly covers all possible GitHub Copilot username variations while maintaining compatibility with existing entries.
Changes
Fixes #30.
💡 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.