oxidecomputer / oxidecomputer/buildomat

GitHub is hiding old checks, making log retrieval difficult

Open
#110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
72
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I went to go look at Buildomat logs for https://github.com/oxidecomputer/transceiver-control/commit/4aac6125a8e6cefbb71d9f8a3d1fe6704207d476 and discovered that GitHub is no longer showing the checks interface for commits beyond a certain time frame. (The cutoff is somewhere between 409 and 416 days ago.)

They are also not present in the API:

$ curl https://api.github.com/repos/oxidecomputer/transceiver-control/commits/4aac6125a8e6cefbb71d9f8a3d1fe6704207d476/check-runs
{
  "total_count": 0,
  "check_runs": [

  ]
}

By design Buildomat requires going through the GitHub checks interface to view logs so that you, in theory, are authorized to view the repository in order to get the log output and the job artefacts.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the missing checks and empty check-runs response for commit 4aac6125a8e6cefbb71d9f8a3d1fe6704207d476, then review Buildomat's GitHub checks and log-access flow. The issue names no repository file or test, and it does not define a change or acceptance criteria for cases where GitHub no longer exposes the checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
ci-cd
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.