Repository navigation
[tracer] Reports linked to GitHub issues: link, follow, tell, same failure - #53
Draft
DraChimeraVee wants to merge 6 commits into
Draft
DraChimeraVee wants to merge 6 commits into
DraChimeraVee wants to merge 6 commits into
Conversation
The repository's issues never name a game, and the issue held the game's title and title ID, the player's note and the log's last lines (a path to a dump names the game). The issue is titled by the report's signature and console; a title ID in a value is <game>, a value naming a game's file is cut whole, and the note and last lines stay on the report's page, which the issue links. Signed-off-by: AO55 <AO55@reden-emu.dev>
An approval opens a new issue; a report of a failure an issue already tracks had no way to point at it. "@tracer link 12 1234" (or a reply with "@tracer link 1234"), from those who approve, checks the issue or pull request on GitHub, keeps it as an approval's, and comments on it with the report's page, so each links to the other; "unlink" takes it out. Signed-off-by: AO55 <AO55@reden-emu.dev>
… out A report's issue was filed and forgotten: nothing on its page said it was fixed, and the player who sent it never heard. Every 10 minutes Tracer asks GitHub how each linked issue or pull request stands, keeps the pull request that fixed it and the first nightly that has its commit, and shows them on the page and in the JSON; with TRACER_NOTIFY=reply or ping (off by default) it replies to the report's message once that nightly is out. Signed-off-by: AO55 <AO55@reden-emu.dev>
…o their issue Twenty-one reports of the live site repeat a game's failure another report has, and nothing said so, nor kept an approval from opening one issue each. A new report's reply, its page and its JSON name the newest five reports with its signature and their issues; an approval of a report whose game and signature a linked report has links it to that issue, with a comment, and opens none. Signed-off-by: AO55 <AO55@reden-emu.dev>
…tall Signed-off-by: AO55 <AO55@reden-emu.dev>
DraChimeraVee
force-pushed
the
dravee/tracer/issue-links
branch
from
November 17, 2026 16:08
45ae166 to
7581d9a
Compare
The title is the report's signature, a log's words that may hold a "#12", which GitHub links to the repository's own issue 12. Signed-off-by: AO55 <AO55@reden-emu.dev>
DraChimeraVee
force-pushed
the
dravee/tracer/issue-links
branch
from
November 17, 2026 16:11
1af7eb0 to
aad5819
Compare
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.
Reports and GitHub issues, both ways. Stacked on #52 (same files: the database's version,
report.c).[tracer] An approved report's issue names no game: the repository's issues never name a game, and the issue held the game's title and title ID, the player's note and the log's last lines (a path to a dump names the game). It is titled by the report's signature and console; a title ID in a value is<game>, a value naming a game's file is cut whole; the report's page, linked, has the rest.[tracer] Link a report to an issue that exists: link and unlink:@Tracer link 12 1234(or a reply with@Tracer link 1234), from those who approve, checks the issue or pull request on GitHub, keeps it as an approval's and comments on it with the report's page;unlinktakes it out.[tracer] Follow a report's issue, and tell its sender once the fix is out: every 10 minutes, one GraphQL query for the linked issues and pull requests: their state on the page and in the JSON, the pull request that fixed each (merged, or the one whose merge closed the issue as completed) and the first nightly that has its commit (compare). WithTRACER_NOTIFY=replyorping(off by default) Tracer replies to the report's message once that nightly is out.[tracer] Name the reports of the same failure, and link an approval to their issue: a new report's reply, page and JSON name the newest five reports with its signature (21 reports of the live site repeat a game's failure); an approval of a report whose game and signature a linked report has links it to that issue instead of opening another.The token needs Pull requests and Contents read beside Issues read and write (the docs and the env sample say so). New tests for each against a fake GitHub, and mutants for who links, when a sender is told and the approval of a known failure.