-
-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Description
Short Summary
The governance engine incorrectly updates the last_activity date and logs an ACTIVITY_UPDATE event for contributors based on their global GitHub activity, rather than their activity specifically within this repository.
Steps to Reproduce
- Identify a contributor in
governance/contributors.yaml. - Ensure this contributor performs no actions (commits, comments) in the
gitmeshrepository for a few days. - Have the contributor perform an action on a different public GitHub repository (updating their global event feed).
- Run the governance sync workflow.
Expected Behavior
The last_activity date should only update if the user has performed an action (commit, PR, issue, comment) specifically within the gitmesh repository.
Actual Behavior
The bot detects the new date from the user's global public events, updates the last_activity field in contributors.yaml, and logs an ACTIVITY_UPDATE event in the history, implying the user was active in gitmesh.
Environment
- OS: Windows 11
- Browser: Brave
Additional Context
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working