-
Notifications
You must be signed in to change notification settings - Fork 120
Description
Describe the bug
Problem: In #35 (comment), a new contributor followed the instructions given in #35 (comment)
I followed up, per instructions, by adding a comment to recheck.
Bug: the bot did not recheck.
To reproduce
See the steps taken in #35
Expected behavior
The F5 bot should write info directly to the signature.json database in https://github.com/f5/f5-cla-data . My research suggests this is done almost immediately after the user adds a comment with "I have hereby read the F5 CLA and agree to its terms"
Your environment
- Version/release of this project or specific commit
- Target deployment platform
Additional context
I've found a "working" instance of .github/workflows/f5-cla.yml in https://github.com/nginx/agent/, which wrote info to the signature.json file in that repo as of December 27, 2024.
(Unknown -- could the issue be related to the new year)
Sensitive Information
Remember to redact any sensitive information such as authentication credentials or license keys.