CHANGELOG.md and CONTRIBUTORS.md cite PR #632 and GitHub user @Voyagerroc-Lab, neither of which exist

Open Beginner friendly
#689 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Review the v2.3.0 entry in CHANGELOG.md and the attribution entries in CONTRIBUTORS.md, including the Explainers CODEOWNERS-attribution table. Verify the references with the listed GitHub commands, then remove or correct the nonexistent account and PR attribution in all mentioned locations; done means the files consistently describe the change without fabricated credits.

Written by the indexing model from the issue text.

Description

bug documentation

Where: CHANGELOG.md (v2.3.0 entry, "roc-curve-auc.md" bullet, line ~29), CONTRIBUTORS.md (line ~401-405, "Erol Tasci - [@Voyagerroc-Lab]" entry, and the Explainers CODEOWNERS-attribution table at line ~416).

The gap: both files credit a fix to explainers/roc-curve-auc.md as "closes #623, by @Voyagerroc-Lab, #632". Neither the PR nor the GitHub account actually exist.

Repro:

$ gh pr view 632 --repo yakew7/Fair-Code
GraphQL: Could not resolve to a PullRequest with the number of 632.

$ curl -s -o /dev/null -w "%{http_code}\n" https://github.com/yakew7/Fair-Code/pull/632
404

$ gh api users/Voyagerroc-Lab
{"message":"Not Found", "status":"404"}

$ gh api "search/users?q=Voyagerroc-Lab"
(empty result)

$ gh api repos/yakew7/Fair-Code/commits/530b58d/pulls
(empty - zero associated pull requests)

$ gh api repos/yakew7/Fair-Code/issues/623/timeline --jq '.[]|select(.event=="closed")|{event,source}'
{"event":"closed","source":null}   # closed directly, not via any linked PR

The local commit (530b58d, "docs: clarify COMPAS audit target (#632)") is real and its content matches what CHANGELOG claims - but GitHub confirms it was never part of any pull request, #632 was never a real issue/PR number in this repo, and the credited account is unreachable via both the users API and search API. Every other community-PR attribution in the same v2.3.0 changelog block (#634, #633, #631, #630, #629) checked out as genuine, so this is an isolated fabrication, not a pattern.

Fix direction: remove the false "@Voyagerroc-Lab, #632" attribution from both files (and the Explainers CODEOWNERS-attribution table); credit the change as a direct/self-fix (no PR) like the other unattributed items in the same changelog entry, or investigate the actual authorship of commit 530b58d.

Dominant language
HTML
Stars
47
Forks
45
Avg merge
1h 56m
Merged PRs (30d)
96

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/Fair-Code

All issues in yakew7/Fair-Code

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.