ci: check arXiv citations on pull requests - #88
Open
mahirhir wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
This adds one workflow file: .github/workflows/citation-check.yml.
PRs to this repo are often "Add paper: <title>" (for example #80, "Add paper: Beyond Superficial Forgetting: Thorough Unlearning Through Knowledge Density Estimation and Block Re-Insertion"). This workflow reads a PR's body and any changed markdown, checks the arXiv IDs and DOIs it cites against the real record (arXiv's abstract API, DOI content negotiation), and comments if a claimed title doesn't match the real one.
Report-only: fail-on-mismatch defaults to off, so it never blocks a PR by itself.
It reads only that PR's own content. The only outbound calls it makes are to export.arxiv.org and doi.org, to confirm a citation is real.
It uses pull_request_target so the comment lands on PRs from forks too. The action never checks out or runs the PR's code, only reads it through the GitHub API, so the usual pull_request_target risk (running fork code with a privileged token) doesn't apply here.
Known limits are listed at the top of the README, for example pre-2007 arXiv IDs aren't detected.
Real run for reference: mahirhir/cjk-failure-corpus#1
Close this if it's not a fit, that's fine.