Skip to content

fix: use last_edited_at instead of updated_at for post-merge edit detection #373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Grizouforever wants to merge 1 commit into from
+4 −1
Closed

fix: use last_edited_at instead of updated_at for post-merge edit detection #373

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion gittensor/validator/issue_discovery/scoring.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,10 @@ def _collect_issues_from_prs(
continue # No score for unsolved issues

# Anti-gaming: post-merge edit detection
if issue.updated_at and pr.merged_at and issue.updated_at > pr.merged_at:
# Use last_edited_at (body/title edits) instead of updated_at (any activity
# including comments, labels, and the closing event itself which always
# updates updated_at to >= merged_at, penalizing all solved issues)
if issue.last_edited_at and pr.merged_at and issue.last_edited_at > pr.merged_at:
bt.logging.info(
f'Issue #{issue.number} edited after PR #{pr.number} merge — 0 score, counts as closed'
)
Expand Down