Open
Conversation
Collaborator
sadrasabouri
left a comment
There was a problem hiding this comment.
Can you send me the created dataset in Slack so I can start from the byproduct?
Owner
Author
|
Just pushed some new commits to this pr addressing all the issues we discussed from our last meeting. Sending finished dataset in slack |
sadrasabouri
requested changes
Feb 27, 2026
Collaborator
sadrasabouri
left a comment
There was a problem hiding this comment.
I requested changes for some nitpicks. Since I still can't run the project, I can't test the functionality, but we can save that for later since it's more about reproducibility.
Comment on lines
+152
to
+154
| CACHE_DIR_DEFAULT = f"{REPO}_cache" | ||
| RESOLVE_CACHE_FILENAME = "resolve_cache.json" | ||
| PAIRS_FILENAME = "pairs.json" |
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
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 repo is a pipeline for building a JSONL dataset. It uses the GitHub GraphQL API to discover merged PRs and their closing issues, producing (issue_id, pr_id) pairs without changelog parsing. For each pair it clones the repo (if needed), creates Git branches (base and human from the PR merge commit), and optionally runs the Cursor agent to add cursor and cursor-creative branches. The pipeline is master controlled by main.py subcommands: resolve (get pr/issue and pair), extract (per-pair branch setup and extract cache), apply-cursor (agent runs and branch updates in the cache), and build (read extract cache and write dataset.jsonl with project, issue/PR text, hashes, and base-vs-human and base-vs-cursor diffs). Caches (resolve, pairs, extract) live under a configurable _cache directory;
For workflow logic and specific functionality/usage, checkout README.md