build(release): 38 contributed pipeline lists from #14, 12,001 pipelines; COMPUTE_MOST raised to 3584 #1688

Merged
HumanBean merged 1 commit from HumanBean/Longshot:build/pipelines-from-14 into main 2026-11-19 02:41:39 +00:00
Owner

Type: build · Risk: low · Tested on: none (the sources' check only) · Needs: a first start on any GPU

TL;DR

Since the fork, 40 players have attached the pipeline lists their game wrote to the Submit your pipelines issue, and none of them was in the release yet. This PR adds 38 of them (two held nothing new), so the first start prepares 12,001 more pipelines before the title: 75,921 in all, up from 63,920. That should mean fewer stutters the first time a player reaches an area. The lists pass the repository's own check, and the merge stays deterministic.

Breakdown

  • Who it helps: every player on their first visit to an area, especially in dungeons, bosses and later areas that the existing lists missed.
  • What was wrong: pipelines the shipped list doesn't name get built during play, which causes a stutter or a white wash the first time.
  • What changes: 38 new contrib/ lists with their notes; the merged shipped list grows by 12,001 pipelines (10,625 graphics, 266 mesh, 1,110 compute programs), and COMPUTE_MOST goes from 2560 to 3584 so the check accepts the 3,309 compute programs the merge now names.
  • What does not change: no code; the existing lists, the tour's list and the merge order stay as they were.
  • How it was checked: each sent list passed nx2/pipeline_states.py --check before add, and nx2/pipeline_states.py check passes on the result.
  • What is still open: the extra cost of the larger compute set has not been measured again (see Risks), and no game run has been done.
  • Risk: low to medium: a longer first-start preparation, and roughly 1 GB more memory held for compute programs on each start.

Why

Issue #14 asks players to send the list their game wrote, and promises that we'll merge each one with nx2/pipeline_states.py. Forty lists arrived between 2026-11-13 and today, from NVIDIA (GTX 1650 to RTX 5090 D), AMD (RX 6600 to RX 9070 XT, an 890M) and Intel Arc B370, on Windows and Linux, at resolutions from 1536x864 to 5120x1440 and with every upscaler. Several cover a full playthrough or most of the dungeons. See #14.

What changed

Each list was added with nx2/pipeline_states.py add <name> <list> --who "<user> (#14)" ..., in the order the comments were posted. Each new source therefore holds only the pipelines that no list before it has. The notes' GPU, build and settings come from the report the game wrote into each zip (longshot_pipeline_report.txt), and the route comes from the player's comment. Where a field was left blank it is marked "not given".

  • assets/pipeline_states/contrib/: 38 <user>-<gpu>.bin.xz lists and their .md notes (table below).
  • nx2/pipeline_states.py: COMPUTE_MOST 2560 → 3584, with a comment giving the reason and the estimated cost.
  • assets/pipeline_states/README.md: the limit's number.

Not added: MB44's (292 pipelines) and piano_butcher's (142) lists held nothing that the earlier lists don't already have.

How the zips were handled: each attachment was downloaded into its own folder and its members were listed. All 40 held only *_pipeline_states.bin (and, in most, the report text). Only those two members were read, nothing was run, and each list passed --check (exactly a version 2 list, within the sent-list limits) before add.

List Who GPU and driver New pipelines
albeth-rtx-4070-super albeth NVIDIA GeForce RTX 4070 SUPER, driver NVIDIA 621.24 70
ap1017-rtx-4090 ap1017 NVIDIA GeForce RTX 4090, driver NVIDIA 617.42 76
berzercker-rx-9070-xt Berzercker AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.10.1 (LLPC) 3664
bowen26223-rtx-5090-d bowen26223 NVIDIA GeForce RTX 5090 D, driver NVIDIA 621.01 21
chuchothecatlord-rx-6950-xt ChuchoTheCatLord AMD Radeon RX 6950 XT (RADV NAVI21) - radv - Mesa 26.2.6 (LLVM 22.1.8) 329
davyn-rx-6600 Davyn AMD Radeon RX 6600, driver AMD proprietary driver 26.10.1 (AMD proprietary shader compiler) 5
dinotoxic-rtx-3060-ti dinotoxic NVIDIA GeForce RTX 3060 Ti, driver NVIDIA 621.14 12
dnf113abc-arc-b370 dnf113abc Intel(R) Arc(TM) B370 GPU, driver Intel Corporation 101.9175 5
gaborne-rx-9070-xt-2 Gaborne AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) 128
gaborne-rx-9070-xt Gaborne AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) 34
ginkumasho-rtx-4060-laptop ginkumasho NVIDIA GeForce RTX 4060 Laptop GPU, driver NVIDIA 621.24 26
goulagman-rtx-5070 Goulagman NVIDIA GeForce RTX 5070, driver NVIDIA 621.24 46
haplessidiot-rtx-3070 HaplessIdiot NVIDIA GeForce RTX 3070, driver NVIDIA 595.104.02 18
haruhiro88-rtx-5070 Haruhiro88 NVIDIA GeForce RTX 5070, driver NVIDIA 621.24 656
idipzy-rx-6750-xt iDipzy AMD Radeon RX 6750 XT (RADV NAVI22), driver radv Mesa 25.1.5-1pop0175639923122.04~b84bab8 12
jabbaxipil-rtx-4070 jabbaxipil NVIDIA GeForce RTX 4070, driver NVIDIA 615.71.09 225
losava-rtx-3080 losava NVIDIA GeForce RTX 3080, driver NVIDIA 616.64 7
mr-r00k-rtx-3080-ti Mr_R00k NVIDIA GeForce RTX 3080 Ti, driver NVIDIA 617.42 26
mustardtiger-rx-9070-xt MustardTiger AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) 84
poty87-rtx-3090 poty87 NVIDIA GeForce RTX 3090, driver NVIDIA 621.14 130
razytos-rx-9070-xt Razytos AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) 921
realredrich-890m realredrich AMD Radeon(TM) 890M Graphics, driver AMD proprietary driver 26.10.1 (LLPC) 21
rhinomcd-rtx-3080-ti rhinomcd NVIDIA GeForce RTX 3080 Ti, driver NVIDIA 615.78.08 87
rnc777-rtx-5070-ti rnc777 NVIDIA GeForce RTX 5070 Ti, driver NVIDIA 621.24 4
salvy931-rx-9070-xt salvy931 AMD Radeon RX 9070 XT, driver 2.0.416 1500
senhorcotrim-rx-7600 SenhorCotrim AMD Radeon RX 7600, driver AMD proprietary driver 26.11.1 (LLPC) 74
silverxp-rtx-4060-ti silverxp NVIDIA GeForce RTX 4060 Ti, driver NVIDIA 617.14 47
sneakymiata-rtx-3050-laptop sneakymiata NVIDIA GeForce RTX 3050 Laptop GPU, driver NVIDIA 596.49 1
thebobdoleexperience-rtx-4070-ti TheBobDoleExperience NVIDIA GeForce RTX 4070 Ti, driver NVIDIA 620.70.06 1384
treverflume-rtx-3060-laptop treverflume NVIDIA GeForce RTX 3060 Laptop GPU, driver NVIDIA 615.78.08 577
trulyneochaos-rtx-4070-laptop trulyneochaos NVIDIA GeForce RTX 4070 Laptop GPU, driver NVIDIA 610.62 7
veridor-rx-9070 Veridor AMD Radeon RX 9070 (RADV GFX1201), driver radv Mesa 26.2.6-arch3.1 597
wasabitws-gtx-1650 wasabitws NVIDIA GeForce GTX 1650, driver NVIDIA 621.24 3
watauro-rtx-3060 Watauro NVIDIA GeForce RTX 3060, driver NVIDIA 621.14 781
x-yohe-x-rx-6600 X_Yohe_X AMD Radeon RX 6600, driver AMD proprietary driver 26.10.1 (AMD proprietary shader compiler) 304
xerphyl-rtx-3070-ti Xerphyl NVIDIA GeForce RTX 3070 Ti, driver NVIDIA 621.01 283
yeetbot90-rx-9070-xt Yeetbot90 AMD Radeon RX 9070 XT, driver 26.10.1 (Ryzen 9 7900X), OS not given 191
zethryder-rtx-2070 ZethRyder NVIDIA GeForce RTX 2070, driver NVIDIA 621.14 143

Measurements

Verdict: nothing measured in the game. The counts below come from nx2/pipeline_states.py check.

Before: main @ 10fab152 After: this PR @ 0623986a
merged pipelines 63,920 75,921
graphics 57,687 68,312
mesh 4,034 4,300
compute programs 2,199 3,309
programs 22,785 27,125

Flags and settings

None. (COMPUTE_MOST is a bound in the build tool's check, not a switch.)

Testing

Tested: nx2/pipeline_states.py --check on each of the 40 sent lists (all version 2, all accepted), then nx2/pipeline_states.py check on the sources after the adds (passes, merged: 75921 pipelines (compute 3309, graphics 68312, mesh 4300) of 27125 programs, version 2). The test suite was not run on this PC.

Not tested: a game run. Opened with --force at the maintainer's request: no game code changes, only the data the first start prepares.

Must be tested:

  • Any GPU, a fresh game folder built from this branch: let the first start's shader preparation run to the title and play a few minutes. Expect it to finish without errors and the log to report more pipelines prepared than on main; note the preparation time and VRAM against main (Test Farm: @Beanstalk a cold first start of this branch against main, preparation time and memory at the title).

Risks

What could break: the first start's preparation takes longer with 12,001 more pipelines. The 1,110 more compute programs are kept ready on every start: by the 2026-11-12 measurement in nx2/pipeline_states.py that is about 1 MB and a few ms of precompile each, so roughly 1.1 GB more memory and 2 to 3 s more per start. That matters most on 8 GB cards and integrated GPUs. If it turns out too costly, prune the compute records rather than the graphics ones.

Turning it off: revert the commit, or lower COMPUTE_MOST and drop the newest lists.

Compatibility: a player's first start after updating prepares the new pipelines once. Saves, options and caches are otherwise unchanged.

Issues

See #14 (it stays open for more lists).

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.

🤖 Generated with Claude Code

**Type:** build · **Risk:** low · **Tested on:** none (the sources' check only) · **Needs:** a first start on any GPU ## TL;DR Since the fork, 40 players have attached the pipeline lists their game wrote to the Submit your pipelines issue, and none of them was in the release yet. This PR adds 38 of them (two held nothing new), so the first start prepares 12,001 more pipelines before the title: 75,921 in all, up from 63,920. That should mean fewer stutters the first time a player reaches an area. The lists pass the repository's own check, and the merge stays deterministic. ## Breakdown - **Who it helps:** every player on their first visit to an area, especially in dungeons, bosses and later areas that the existing lists missed. - **What was wrong:** pipelines the shipped list doesn't name get built during play, which causes a stutter or a white wash the first time. - **What changes:** 38 new `contrib/` lists with their notes; the merged shipped list grows by 12,001 pipelines (10,625 graphics, 266 mesh, 1,110 compute programs), and `COMPUTE_MOST` goes from 2560 to 3584 so the check accepts the 3,309 compute programs the merge now names. - **What does not change:** no code; the existing lists, the tour's list and the merge order stay as they were. - **How it was checked:** each sent list passed `nx2/pipeline_states.py --check` before `add`, and `nx2/pipeline_states.py check` passes on the result. - **What is still open:** the extra cost of the larger compute set has not been measured again (see Risks), and no game run has been done. - **Risk:** low to medium: a longer first-start preparation, and roughly 1 GB more memory held for compute programs on each start. ## Why Issue #14 asks players to send the list their game wrote, and promises that we'll merge each one with `nx2/pipeline_states.py`. Forty lists arrived between 2026-11-13 and today, from NVIDIA (GTX 1650 to RTX 5090 D), AMD (RX 6600 to RX 9070 XT, an 890M) and Intel Arc B370, on Windows and Linux, at resolutions from 1536x864 to 5120x1440 and with every upscaler. Several cover a full playthrough or most of the dungeons. See #14. ## What changed Each list was added with `nx2/pipeline_states.py add <name> <list> --who "<user> (#14)" ...`, in the order the comments were posted. Each new source therefore holds only the pipelines that no list before it has. The notes' GPU, build and settings come from the report the game wrote into each zip (`longshot_pipeline_report.txt`), and the route comes from the player's comment. Where a field was left blank it is marked "not given". - `assets/pipeline_states/contrib/`: 38 `<user>-<gpu>.bin.xz` lists and their `.md` notes (table below). - `nx2/pipeline_states.py`: `COMPUTE_MOST` 2560 → 3584, with a comment giving the reason and the estimated cost. - `assets/pipeline_states/README.md`: the limit's number. Not added: MB44's (292 pipelines) and piano_butcher's (142) lists held nothing that the earlier lists don't already have. How the zips were handled: each attachment was downloaded into its own folder and its members were listed. All 40 held only `*_pipeline_states.bin` (and, in most, the report text). Only those two members were read, nothing was run, and each list passed `--check` (exactly a version 2 list, within the sent-list limits) before `add`. | List | Who | GPU and driver | New pipelines | |---|---|---|---| | `albeth-rtx-4070-super` | albeth | NVIDIA GeForce RTX 4070 SUPER, driver NVIDIA 621.24 | 70 | | `ap1017-rtx-4090` | ap1017 | NVIDIA GeForce RTX 4090, driver NVIDIA 617.42 | 76 | | `berzercker-rx-9070-xt` | Berzercker | AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.10.1 (LLPC) | 3664 | | `bowen26223-rtx-5090-d` | bowen26223 | NVIDIA GeForce RTX 5090 D, driver NVIDIA 621.01 | 21 | | `chuchothecatlord-rx-6950-xt` | ChuchoTheCatLord | AMD Radeon RX 6950 XT (RADV NAVI21) - radv - Mesa 26.2.6 (LLVM 22.1.8) | 329 | | `davyn-rx-6600` | Davyn | AMD Radeon RX 6600, driver AMD proprietary driver 26.10.1 (AMD proprietary shader compiler) | 5 | | `dinotoxic-rtx-3060-ti` | dinotoxic | NVIDIA GeForce RTX 3060 Ti, driver NVIDIA 621.14 | 12 | | `dnf113abc-arc-b370` | dnf113abc | Intel(R) Arc(TM) B370 GPU, driver Intel Corporation 101.9175 | 5 | | `gaborne-rx-9070-xt-2` | Gaborne | AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) | 128 | | `gaborne-rx-9070-xt` | Gaborne | AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) | 34 | | `ginkumasho-rtx-4060-laptop` | ginkumasho | NVIDIA GeForce RTX 4060 Laptop GPU, driver NVIDIA 621.24 | 26 | | `goulagman-rtx-5070` | Goulagman | NVIDIA GeForce RTX 5070, driver NVIDIA 621.24 | 46 | | `haplessidiot-rtx-3070` | HaplessIdiot | NVIDIA GeForce RTX 3070, driver NVIDIA 595.104.02 | 18 | | `haruhiro88-rtx-5070` | Haruhiro88 | NVIDIA GeForce RTX 5070, driver NVIDIA 621.24 | 656 | | `idipzy-rx-6750-xt` | iDipzy | AMD Radeon RX 6750 XT (RADV NAVI22), driver radv Mesa 25.1.5-1pop0~1756399231~22.04~b84bab8 | 12 | | `jabbaxipil-rtx-4070` | jabbaxipil | NVIDIA GeForce RTX 4070, driver NVIDIA 615.71.09 | 225 | | `losava-rtx-3080` | losava | NVIDIA GeForce RTX 3080, driver NVIDIA 616.64 | 7 | | `mr-r00k-rtx-3080-ti` | Mr_R00k | NVIDIA GeForce RTX 3080 Ti, driver NVIDIA 617.42 | 26 | | `mustardtiger-rx-9070-xt` | MustardTiger | AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) | 84 | | `poty87-rtx-3090` | poty87 | NVIDIA GeForce RTX 3090, driver NVIDIA 621.14 | 130 | | `razytos-rx-9070-xt` | Razytos | AMD Radeon RX 9070 XT, driver AMD proprietary driver 26.11.1 (LLPC) | 921 | | `realredrich-890m` | realredrich | AMD Radeon(TM) 890M Graphics, driver AMD proprietary driver 26.10.1 (LLPC) | 21 | | `rhinomcd-rtx-3080-ti` | rhinomcd | NVIDIA GeForce RTX 3080 Ti, driver NVIDIA 615.78.08 | 87 | | `rnc777-rtx-5070-ti` | rnc777 | NVIDIA GeForce RTX 5070 Ti, driver NVIDIA 621.24 | 4 | | `salvy931-rx-9070-xt` | salvy931 | AMD Radeon RX 9070 XT, driver 2.0.416 | 1500 | | `senhorcotrim-rx-7600` | SenhorCotrim | AMD Radeon RX 7600, driver AMD proprietary driver 26.11.1 (LLPC) | 74 | | `silverxp-rtx-4060-ti` | silverxp | NVIDIA GeForce RTX 4060 Ti, driver NVIDIA 617.14 | 47 | | `sneakymiata-rtx-3050-laptop` | sneakymiata | NVIDIA GeForce RTX 3050 Laptop GPU, driver NVIDIA 596.49 | 1 | | `thebobdoleexperience-rtx-4070-ti` | TheBobDoleExperience | NVIDIA GeForce RTX 4070 Ti, driver NVIDIA 620.70.06 | 1384 | | `treverflume-rtx-3060-laptop` | treverflume | NVIDIA GeForce RTX 3060 Laptop GPU, driver NVIDIA 615.78.08 | 577 | | `trulyneochaos-rtx-4070-laptop` | trulyneochaos | NVIDIA GeForce RTX 4070 Laptop GPU, driver NVIDIA 610.62 | 7 | | `veridor-rx-9070` | Veridor | AMD Radeon RX 9070 (RADV GFX1201), driver radv Mesa 26.2.6-arch3.1 | 597 | | `wasabitws-gtx-1650` | wasabitws | NVIDIA GeForce GTX 1650, driver NVIDIA 621.24 | 3 | | `watauro-rtx-3060` | Watauro | NVIDIA GeForce RTX 3060, driver NVIDIA 621.14 | 781 | | `x-yohe-x-rx-6600` | X_Yohe_X | AMD Radeon RX 6600, driver AMD proprietary driver 26.10.1 (AMD proprietary shader compiler) | 304 | | `xerphyl-rtx-3070-ti` | Xerphyl | NVIDIA GeForce RTX 3070 Ti, driver NVIDIA 621.01 | 283 | | `yeetbot90-rx-9070-xt` | Yeetbot90 | AMD Radeon RX 9070 XT, driver 26.10.1 (Ryzen 9 7900X), OS not given | 191 | | `zethryder-rtx-2070` | ZethRyder | NVIDIA GeForce RTX 2070, driver NVIDIA 621.14 | 143 | ## Measurements **Verdict:** nothing measured in the game. The counts below come from `nx2/pipeline_states.py check`. | | Before: main @ 10fab152 | After: this PR @ 0623986a | |---|---|---| | merged pipelines | 63,920 | 75,921 | | graphics | 57,687 | 68,312 | | mesh | 4,034 | 4,300 | | compute programs | 2,199 | 3,309 | | programs | 22,785 | 27,125 | ### Flags and settings None. (`COMPUTE_MOST` is a bound in the build tool's check, not a switch.) ## Testing **Tested:** `nx2/pipeline_states.py --check` on each of the 40 sent lists (all version 2, all accepted), then `nx2/pipeline_states.py check` on the sources after the adds (passes, `merged: 75921 pipelines (compute 3309, graphics 68312, mesh 4300) of 27125 programs, version 2`). The test suite was not run on this PC. **Not tested:** a game run. Opened with `--force` at the maintainer's request: no game code changes, only the data the first start prepares. **Must be tested:** - Any GPU, a fresh game folder built from this branch: let the first start's shader preparation run to the title and play a few minutes. Expect it to finish without errors and the log to report more pipelines prepared than on main; note the preparation time and VRAM against main (Test Farm: `@Beanstalk` a cold first start of this branch against main, preparation time and memory at the title). ## Risks **What could break:** the first start's preparation takes longer with 12,001 more pipelines. The 1,110 more compute programs are kept ready on every start: by the 2026-11-12 measurement in `nx2/pipeline_states.py` that is about 1 MB and a few ms of precompile each, so roughly 1.1 GB more memory and 2 to 3 s more per start. That matters most on 8 GB cards and integrated GPUs. If it turns out too costly, prune the compute records rather than the graphics ones. **Turning it off:** revert the commit, or lower `COMPUTE_MOST` and drop the newest lists. **Compatibility:** a player's first start after updating prepares the new pipelines once. Saves, options and caches are otherwise unchanged. ## Issues See #14 (it stays open for more lists). ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [ ] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [ ] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [ ] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
build(release): 38 contributed pipeline lists from #14, 12,001 pipelines; COMPUTE_MOST raised to 3584
Some checks failed
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 14s
PR description / Description follows the template (pull_request_target) Failing after 6s
0623986adb
Each list players sent to the Submit your pipelines issue, added with
nx2/pipeline_states.py add in the order they were posted (each holds only what
no list before it has). Two of the 40 (MB44, piano_butcher) held nothing new.

Their play dispatched 1,110 compute programs no list had, taking the merged
list to 3,309, past COMPUTE_MOST (2560): raised to 3584, not measured again.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean changed title from WIP: build(release): 38 contributed pipeline lists from #14, 12,001 pipelines; COMPUTE_MOST raised to 3584 to build(release): 38 contributed pipeline lists from #14, 12,001 pipelines; COMPUTE_MOST raised to 3584 2026-11-19 02:41:32 +00:00
HumanBean deleted branch build/pipelines-from-14 2026-11-19 02:41:39 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1688
No description provided.