Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🤖 ci: follow-ups after moving PR jobs to the merge queue (#7334)

Closed
  • Is something wrong?
#7,340 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, github-actions, typescript
Domain
ci-cd, devops

Research direction

Read .github/workflows/pr.yml and the docker path filter, then review the merge-queue runs and 7-day cost data described in the issue. Decide whether to restore Test / E2E to PR pushes, include any src paths in Docker coverage, and address the skipped matrix job name; completion depends on those measurements and decisions.

Written by the indexing model from the issue text.

Description

Follow-ups from the Depot cost stack #7333 / #7334. Owner: ThomasK33 (or whoever lands the next CI change). Trigger: the first 40 merge-queue runs after #7334 merges, and a 7-day cost check.

  1. Rollback trigger. If the moved jobs (Test / E2E, Test / Bug-bash sandbox, Smoke / Server, Build / Linux, Build / VS Code) fail in more than 3 of the first 40 merge-queue runs after #7334, move Test / E2E back to PR pushes (one if: line in .github/workflows/pr.yml).
  2. Cost check. After 7 days, measure 16-vCPU-equal minutes per PR run. Target: 30 or fewer (109 before the stack).
  3. Docker coverage. Smoke / Docker no longer runs on src/**-only PRs (context #5605). Decide whether any src path belongs back in the docker filter.
  4. Cosmetic. A skipped Test / E2E matrix job shows its unexpanded name (Test / E2E (${{ matrix.os }}…)) in the PR checks list.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $11.70

Dominant language
TypeScript
Stars
2.1k
Forks
139
Avg merge
3h 24m
Merged PRs (30d)
954

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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 coder/xum

All issues in coder/xum

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.