fix: scope governance activity tracking to repository-specific events#373
Open
Sanchit2662 wants to merge 1 commit into
Open
Conversation
Replace global user GitHub activity API (/users/{username}/events/public) with
repo-scoped queries for commits, PRs, and comments. This ensures contributors
are only marked active/inactive based on their activity in the gitmesh repository,
not unrelated activity in other public repositories.
Fixes LF-Decentralized-Trust-labs#356
Signed-off-by: Sanchit2662 <sanchit2662@gmail.com>
Author
|
@RAWx18 , Please review the fix. |
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
I fixed the governance activity tracking bug by scoping it to only track activity in the gitmesh repository. Instead of checking a user's global GitHub activity (which included commits to any public repo), I now query four repo-specific endpoints: commits, pull requests, issue comments, and PR review comments. This ensures contributors are only marked inactive if they haven't done anything in this repository for 90+ days, not in other projects.
Related Issue
Fixes #356
Type of Change
How Was This Tested?
Notes:
The governance workflow runs on a GitHub Actions schedule (weekly Friday at 01:30 UTC) and requires: 1. Live GitHub API access with a valid GITHUB_TOKEN
2. A real gitmesh repository clone with governance files
3. Network calls to GitHub's API endpoints
CE & Security Check