headscale/.github
Kristoffer Dalby 174e409da6
Some checks are pending
Build / build-nix (push) Waiting to run
Build / build-cross (GOARCH=amd64 GOOS=darwin) (push) Waiting to run
Build / build-cross (GOARCH=amd64 GOOS=linux) (push) Waiting to run
Build / build-cross (GOARCH=arm64 GOOS=darwin) (push) Waiting to run
Build / build-cross (GOARCH=arm64 GOOS=linux) (push) Waiting to run
Check Generated Files / check-generated (push) Waiting to run
NixOS Module Tests / nix-module-check (push) Waiting to run
Tests / test (push) Waiting to run
github: drop nu flatten in needs-more-info timer
The scheduled job has failed every night since 2026-04-13. Two
prior fixes (race-condition guards and splitting the combined
where predicate in #3200) did not address the actual cause:
`flatten` collapses nested records in a list-of-records pipeline,
so after `gh api ... | from json | flatten` the `label` and `user`
columns no longer exist - their fields are lifted to the top
level (with prefix only on naming collisions). `where label.name
== ...` and `where user.type != "Bot"` then both reference a
column that is not there.

`gh api --paginate` already returns a single concatenated JSON
array, so `from json` produces a list of records directly and no
flattening is needed. Drop both `| flatten` calls.

Verified locally with nu 0.108 against the events stream of issue
#3178: without flatten, `where event == "labeled" | where
label.name == "needs-more-info" | last` returns the labeled event
with its `label` record intact.
2026-04-28 16:36:32 +01:00
..
ISSUE_TEMPLATE github: update issue template contact links 2026-02-09 09:51:28 +01:00
label-response github: add support-request automation workflow 2026-02-09 09:51:28 +01:00
workflows github: drop nu flatten in needs-more-info timer 2026-04-28 16:36:32 +01:00
CODEOWNERS add nblock to doc owners (#2207) 2024-11-04 10:12:50 -06:00
FUNDING.yml Add ko-fi sponsor button 2022-12-22 17:25:49 +01:00
pull_request_template.md Add contributing document 2024-04-29 23:04:02 +02:00
renovate.json update readme and templates to clarify scope (#1437) 2023-05-10 08:03:13 +01:00