docs(perf): the player guide says the game sends the performance batches, not the launcher #1775

Open
mooki wants to merge 1 commit from mooki/Longshot:docs/readme-game-sends-perf into main
Member

Summary

Since #1530 the game sends the five-minute performance batches itself, and the performance statistics reference (docs/dev/reference/profiling.md) says so, but the player guide's "what Longshot connects to" list (docs/user/updates-and-saves.md) still had the launcher send them at its next start. It now says the game sends them in five-minute batches to the team with the GPU, driver, CPU, OS and renderer, but no paths, user name or ID. This is the sentence #1502's last review suggested. The README row this change was opened against moved with the docs revamp (the README is a landing page now), so the title now names the player guide.

Testing

Tested: Rebased onto main @ 068fb8ebe2 (the docs revamp, #1802; this head 8be546f776, one commit, docs only). The earlier head e0a69cba3 on main @ 3653c9c57 changed one README sentence and the checks that read the README gave the same results as on main there. On this head, test_doc_anchors and test_fs_links pass; the documentation links of the page resolve. The whole suite was not run and nothing was started: a sentence in a Markdown file cannot reach a game or a check that does not read it. Not tested: how the page looks rendered on the website.

Still to test:
None

Measurements

Nothing to measure: a documentation sentence.

Risks

Nothing the game or a build reads. A revert is enough; players see the corrected sentence.

Checklist

Ready for review

  • One topic, on current main; the title is a Conventional Commit.
  • Tested on my own PC, in the game for a change the game runs, as Testing says.
  • mise run test passes (any failure that also fails on main is named): the focused checks named in Tested ran; docs only, the whole suite was not run (the checks that read the page ran)
  • Measured against main, or Measurements says why there is nothing to measure.
  • No game files, build output or hand-edited generated files; third_party/ untouched; nothing GPL-incompatible.

When it applies

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

Ready to merge

  • Everything in Still to test has run, its results in Tested.
  • Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers").
  • Approved in review, every comment answered.
  • CI passes on the head; on current main, measured again or a comment says why the numbers still hold.

New on this forge; not opened on GitHub.

## Summary Since #1530 the game sends the five-minute performance batches itself, and the performance statistics reference (`docs/dev/reference/profiling.md`) says so, but the player guide's "what Longshot connects to" list (`docs/user/updates-and-saves.md`) still had the launcher send them at its next start. It now says the game sends them in five-minute batches to the team with the GPU, driver, CPU, OS and renderer, but no paths, user name or ID. This is the sentence #1502's last review suggested. The README row this change was opened against moved with the docs revamp (the README is a landing page now), so the title now names the player guide. ## Testing **Tested:** Rebased onto main @ 068fb8ebe2 (the docs revamp, #1802; this head 8be546f776, one commit, docs only). The earlier head `e0a69cba3` on main @ 3653c9c57 changed one README sentence and the checks that read the README gave the same results as on main there. On this head, `test_doc_anchors` and `test_fs_links` pass; the documentation links of the page resolve. The whole suite was not run and nothing was started: a sentence in a Markdown file cannot reach a game or a check that does not read it. Not tested: how the page looks rendered on the website. **Still to test:** None ## Measurements Nothing to measure: a documentation sentence. ## Risks Nothing the game or a build reads. A revert is enough; players see the corrected sentence. ## Checklist ### Ready for review - [x] One topic, on current `main`; the title is a Conventional Commit. - [x] Tested on my own PC, in the game for a change the game runs, as Testing says. - [x] `mise run test` passes (any failure that also fails on `main` is named): the focused checks named in Tested ran; docs only, the whole suite was not run (the checks that read the page ran) - [x] Measured against `main`, or Measurements says why there is nothing to measure. - [x] No game files, build output or hand-edited generated files; `third_party/` untouched; nothing GPL-incompatible. ### When it applies - [x] Docs updated. - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. ### Ready to merge - [ ] Everything in Still to test has run, its results in Tested. - [ ] Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers"). - [ ] Approved in review, every comment answered. - [ ] CI passes on the head; on current `main`, measured again or a comment says why the numbers still hold. --- New on this forge; not opened on GitHub.
docs(perf): the README says the game sends the performance batches, not the launcher
Some checks failed
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
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 11s
PR description / Description follows the template (pull_request_target) Successful in 14s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 15s
CI / Workflow lint (actionlint) (pull_request) Successful in 16s
Third-party parts / As their notes say (pull_request) Successful in 17s
beanstalk/approval approved by mooki (reviewed)
beanstalk/any 1/1 pass
e0a69cba34
Since #1530 the game sends the five-minute batches itself, and docs/performance-statistics.md says the launcher "does
not send". The README's Send performance statistics row, which #1502 edited, still had the launcher send them at its
next start. It now reads "The game sends five-minute batches to the team, with the GPU, driver, CPU, OS and renderer but
no paths, user name or ID.", the sentence #1502's last review suggested.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
mooki changed title from WIP: docs(perf): the README says the game sends the performance batches, not the launcher to docs(perf): the README says the game sends the performance batches, not the launcher 2026-11-19 18:51:48 +00:00
Author
Member

@Beanstalk

@Beanstalk
Member
Beanstalk test farm · an earlier run: commit e0a69cb (the newer results are in a comment below)

Commit e0a69cb · tier reviewed · approved by mooki · dashboard

What will be tested · AI plan (gpt-6.1-terra)

This is a README-only correction, so gameplay cannot verify the changed wording or who sends performance batches. A brief title-screen smoke test compares startup and rendering with main, taking about 10 minutes per tester. A crash, a startup slowdown over 20%, or a substantial screenshot difference fails the plan; the documentation claim itself remains outside the farm's checks.

  • Where: any (any PC, 1-2 reports).
  • title-smoke: from the title screen, then take the picture title to compare with main; 1 run on each side.
  • Measured: crashes, boot time.
  • The PR fails if: it crashes; or a picture differs from main by more than 10%; or boot time is more than 20% above main.
  • Time: about 11 min of game runs per tester (2 game starts), plus the two builds.

Done (started 18:52 UTC, last report 19:24 UTC). Comment @Beanstalk to run it again.

Target Reports Crash Frame p99 (ms) vs main VRAM peak (MB) vs main Result
any · 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3070, 621.24.0 2/1 1 2 none — — pass

Measurements · any

Verdict: pass on any (2/1 report): no rule failed and no PR run crashed.

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0 AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3070, 621.24.0 AMD Ryzen 5 5600X3D 6-Core Processor, 32 GB RAM
Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Before: main @ 3653c9c After: this PR @ e0a69cb
title-smoke · boot time (s) 588.2 563.8 (−4%)

Flags and settings

None: the plan varied no setting, switch or build option.

Markdown for the PR description
## Measurements

**Verdict:** pass on any (2/1 report): no rule failed and no PR run crashed.

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3070, 621.24.0` `AMD Ryzen 5 5600X3D 6-Core Processor, 32 GB RAM`  
Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

| | Before: main @ 3653c9c | After: this PR @ e0a69cb |
|---|---|---|
| title-smoke · boot time (s) | 588.2 | 563.8 (−4%) |

### Flags and settings

None: the plan varied no setting, switch or build option.
<!-- beanstalk:previous --> <details><summary>Beanstalk test farm · an earlier run: commit <code>e0a69cb</code> (the newer results are in a comment below)</summary> Commit `e0a69cb` · tier **reviewed** · approved by mooki · [dashboard](https://beanstalk.magicbean.dev/prs/1775) **What will be tested** · AI plan (`gpt-6.1-terra`) This is a README-only correction, so gameplay cannot verify the changed wording or who sends performance batches. A brief title-screen smoke test compares startup and rendering with main, taking about 10 minutes per tester. A crash, a startup slowdown over 20%, or a substantial screenshot difference fails the plan; the documentation claim itself remains outside the farm's checks. - **Where:** any (any PC, 1-2 reports). - **title-smoke:** from the title screen, then take the picture title to compare with main; 1 run on each side. - **Measured:** crashes, boot time. - **The PR fails if:** it crashes; or a picture differs from main by more than 10%; or boot time is more than 20% above main. - **Time:** about 11 min of game runs per tester (2 game starts), plus the two builds. Done (started 18:52 UTC, last report 19:24 UTC). Comment `@Beanstalk` to run it again. | Target | Reports | Crash | Frame p99 (ms) vs main | VRAM peak (MB) vs main | Result | | --- | --- | --- | --- | --- | --- | | any · 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3070, 621.24.0` | 2/1 [1](https://beanstalk.magicbean.dev/reports/rp_4cf0df4af73ad5ad) [2](https://beanstalk.magicbean.dev/reports/rp_d1543c424533e708) | none | — | — | pass | #### Measurements · any **Verdict:** pass on any (2/1 report): no rule failed and no PR run crashed. Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3070, 621.24.0` `AMD Ryzen 5 5600X3D 6-Core Processor, 32 GB RAM` Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 3653c9c | After: this PR @ e0a69cb | |---|---|---| | title-smoke · boot time (s) | 588.2 | 563.8 (−4%) | ### Flags and settings None: the plan varied no setting, switch or build option. <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** pass on any (2/1 report): no rule failed and no PR run crashed. Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3070, 621.24.0` `AMD Ryzen 5 5600X3D 6-Core Processor, 32 GB RAM` Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 3653c9c | After: this PR @ e0a69cb | |---|---|---| | title-smoke · boot time (s) | 588.2 | 563.8 (−4%) | ### Flags and settings None: the plan varied no setting, switch or build option. ``` </details> </details>
Author
Member

Rebased onto main 068fb8ebe2 (the docs revamp, #1802): head 8be546f776.
Conflict: README.md, which is a landing page now. The sentence about who sends the performance batches lives in the player guide, docs/user/updates-and-saves.md, where it still said the launcher sends them; the change is there, and the title now says the player guide.
Ran: test_doc_anchors and test_fs_links pass.

Rebased onto main 068fb8ebe2 (the docs revamp, #1802): head 8be546f776. Conflict: `README.md`, which is a landing page now. The sentence about who sends the performance batches lives in the player guide, `docs/user/updates-and-saves.md`, where it still said the launcher sends them; the change is there, and the title now says the player guide. Ran: `test_doc_anchors` and `test_fs_links` pass.
mooki force-pushed docs/readme-game-sends-perf from e0a69cba34
Some checks failed
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
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 11s
PR description / Description follows the template (pull_request_target) Successful in 14s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 15s
CI / Workflow lint (actionlint) (pull_request) Successful in 16s
Third-party parts / As their notes say (pull_request) Successful in 17s
beanstalk/approval approved by mooki (reviewed)
beanstalk/any 1/1 pass
to 8be546f776
Some checks failed
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
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
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 12s
CI / Workflow lint (actionlint) (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 14s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 6s
beanstalk/approval approved by mooki (reviewed)
beanstalk/any 1/1 pass
CI / Website build and checks (pull_request) Failing after 2m12s
2026-11-20 01:46:24 +00:00
Compare
Member

Beanstalk test farm

Commit 8be546f · tier reviewed · approved by mooki · dashboard

What will be tested · AI plan (gpt-6.1-terra)

This documentation-only change cannot be verified by a gameplay test. A short title-screen smoke test compares startup time and appearance with main, taking about 10 minutes per tester. A crash, a startup-time increase over 20%, or a substantial screenshot difference fails the plan; it does not check the corrected documentation or telemetry behavior.

  • Where: any (any PC, 1-2 reports).
  • title-smoke: from the title screen, then take the picture title to compare with main; 1 run on each side.
  • Measured: crashes, boot time.
  • The PR fails if: it crashes; or a picture differs from main by more than 10%; or boot time is more than 20% above main.
  • Time: about 11 min of game runs per tester (2 game starts), plus the two builds.

Done (started 01:46 UTC, last report 02:44 UTC). Comment @Beanstalk to run it again.

Target Reports Crash Frame p99 (ms) vs main VRAM peak (MB) vs main Result
any · 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3080 Ti, 621.24.0 2/1 1 2 none — — pass

Measurements · any

Verdict: pass on any (2/1 report): no rule failed and no PR run crashed.

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0 AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3080 Ti, 621.24.0 AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM
Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Before: main @ 068fb8e After: this PR @ 8be546f
title-smoke · boot time (s) 377.4 363.4 (−4%)

Flags and settings

None: the plan varied no setting, switch or build option.

Markdown for the PR description
## Measurements

**Verdict:** pass on any (2/1 report): no rule failed and no PR run crashed.

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3080 Ti, 621.24.0` `AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM`  
Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

| | Before: main @ 068fb8e | After: this PR @ 8be546f |
|---|---|---|
| title-smoke · boot time (s) | 377.4 | 363.4 (−4%) |

### Flags and settings

None: the plan varied no setting, switch or build option.
<!-- beanstalk:sticky --> ### Beanstalk test farm Commit `8be546f` · tier **reviewed** · approved by mooki · [dashboard](https://beanstalk.magicbean.dev/prs/1775) **What will be tested** · AI plan (`gpt-6.1-terra`) This documentation-only change cannot be verified by a gameplay test. A short title-screen smoke test compares startup time and appearance with main, taking about 10 minutes per tester. A crash, a startup-time increase over 20%, or a substantial screenshot difference fails the plan; it does not check the corrected documentation or telemetry behavior. - **Where:** any (any PC, 1-2 reports). - **title-smoke:** from the title screen, then take the picture title to compare with main; 1 run on each side. - **Measured:** crashes, boot time. - **The PR fails if:** it crashes; or a picture differs from main by more than 10%; or boot time is more than 20% above main. - **Time:** about 11 min of game runs per tester (2 game starts), plus the two builds. Done (started 01:46 UTC, last report 02:44 UTC). Comment `@Beanstalk` to run it again. | Target | Reports | Crash | Frame p99 (ms) vs main | VRAM peak (MB) vs main | Result | | --- | --- | --- | --- | --- | --- | | any · 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3080 Ti, 621.24.0` | 2/1 [1](https://beanstalk.magicbean.dev/reports/rp_423cf4bbaee6336f) [2](https://beanstalk.magicbean.dev/reports/rp_a8f77d6509134d23) | none | — | — | pass | #### Measurements · any **Verdict:** pass on any (2/1 report): no rule failed and no PR run crashed. Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3080 Ti, 621.24.0` `AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM` Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 068fb8e | After: this PR @ 8be546f | |---|---|---| | title-smoke · boot time (s) | 377.4 | 363.4 (−4%) | ### Flags and settings None: the plan varied no setting, switch or build option. <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** pass on any (2/1 report): no rule failed and no PR run crashed. Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3080 Ti, 621.24.0` `AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM` Scene: title-smoke, from the title screen; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); title-smoke: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 068fb8e | After: this PR @ 8be546f | |---|---|---| | title-smoke · boot time (s) | 377.4 | 363.4 (−4%) | ### Flags and settings None: the plan varied no setting, switch or build option. ``` </details>
Author
Member

@Beanstalk

@Beanstalk
mooki changed title from docs(perf): the README says the game sends the performance batches, not the launcher to docs(perf): the player guide says the game sends the performance batches, not the launcher 2026-11-20 01:46:50 +00:00
Some checks failed
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
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
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 12s
CI / Workflow lint (actionlint) (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 14s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 6s
beanstalk/approval approved by mooki (reviewed)
beanstalk/any 1/1 pass
CI / Website build and checks (pull_request) Failing after 2m12s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'docs/readme-game-sends-perf:mooki-docs/readme-game-sends-perf'
git switch 'mooki-docs/readme-game-sends-perf'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!1775
No description provided.