You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sync-contributors.yml GitHub Actions workflow has been silently failing for 5+ months due to a file path mismatch. The workflow fetches contributor data correctly but writes it to data/roadmap.json instead of data/community-users.json. It then attempts to commit the unchanged community-users.json file, resulting in no actual updates.
Steps To Reproduce
Go to .github/workflows/sync-contributors.yml
Navigate to line 46
Observe the file path: fs.writeFileSync('data/roadmap.json', ...)
Navigate to line 52: git add data/community-users.json
Notice the mismatch: writes to roadmap.json but adds community-users.json
Check the last update date of data/community-users.json (October 23, 2024)
Run the workflow manually and observe no PR is created
Expected Behavior
The workflow should:
Fetch contributor data from GitHub API ✅
Write data to data/community-users.json ❌ (currently writes to roadmap.json)
Commit and PR the updated community-users.json ❌ (currently commits unchanged file)
Describe the bug
The
sync-contributors.ymlGitHub Actions workflow has been silently failing for 5+ months due to a file path mismatch. The workflow fetches contributor data correctly but writes it todata/roadmap.jsoninstead ofdata/community-users.json. It then attempts to commit the unchangedcommunity-users.jsonfile, resulting in no actual updates.Steps To Reproduce
.github/workflows/sync-contributors.ymlfs.writeFileSync('data/roadmap.json', ...)git add data/community-users.jsonroadmap.jsonbut addscommunity-users.jsondata/community-users.json(October 23, 2024)Expected Behavior
The workflow should:
data/community-users.json❌ (currently writes toroadmap.json)community-users.json❌ (currently commits unchanged file)Screenshots
ScreenCast:
Screencast.from.2026-04-02.03-19-23.webm
Device Information [optional]
Are you working on this issue?
Yes
Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)
No