7 Commits

Include renames

Author	SHA1	Message	Date
github-actions[bot]	cee9066e91	.github: bump 3 action pins	2026-10-13 12:02:59 +02:00
github-actions[bot]	3603418d70	.github: bump 13 action pins	2026-09-28 07:28:19 +02:00
Kristoffer Dalby	174e409da6	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
Kristoffer Dalby	ce5d1ba8f8	github: split nu where in needs-more-info timer ... GitHub's /issues/:n/events endpoint returns a mixed-schema table. Only labeled/unlabeled rows carry a `label` column. Nu's `where` does not short-circuit on missing columns, so the combined predicate `event == "labeled" and label.name == ...` dereferenced `label.name` on every row and crashed on the first non-labeled event with `nu::shell::column_not_found`. The scheduled job has failed every night since 2026-04-13 (the first run with a labeled issue), so no `needs-more-info` issue has been auto-closed. Split into two sequential `where` filters so `label.name` is only accessed on rows that have the column.	2026-04-18 15:39:29 +01:00
Kristoffer Dalby	a7f981e30e	github: fix needs-more-info label race condition ... Replace tiangolo/issue-manager with custom logic that distinguishes bot comments from human responses. The issue-manager action treated all comments equally, so the bot's own instruction comment would trigger label removal on the next scheduled run. Split into two jobs: - remove-label-on-response: triggers on issue_comment from non-bot users, removes the needs-more-info label immediately - close-stale: runs on daily schedule, uses nushell to iterate open needs-more-info issues, checks for human comments after the label was added, and closes after 3 days with no response	2026-02-15 19:42:47 +01:00
Kristoffer Dalby	e0d8c3c877	github: fix needs-more-info label race condition ... Remove the `issues: labeled` trigger from the timer workflow. When both workflows triggered on label addition, the comment workflow would post the bot comment, and by the time the timer workflow ran, issue-manager would see "a comment was added after the label" and immediately remove the label due to `remove_label_on_comment: true`. The timer workflow now only runs on: - Daily cron (to close stale issues) - issue_comment (to remove label when humans respond) - workflow_dispatch (for manual testing)	2026-02-09 10:03:12 +01:00
Kristoffer Dalby	64f23136a2	github: add needs-more-info automation workflow ... Add GitHub Actions automation that helps manage issues requiring additional information from reporters: - Post an instruction comment when 'needs-more-info' label is added, requesting environment details, debug logs from multiple nodes, configuration files, and proper formatting - Automatically remove the label when anyone comments - Close the issue after 3 days if no response is provided - Exempt needs-more-info labeled issues from the stale bot The instruction comment includes guidance on: - Required environment and debug information - Collecting logs from both connecting and connected-to nodes - Proper redaction rules (replace consistently, never remove IPs) - Formatting requirements for attachments and Markdown - Encouragement to discuss on Discord before filing issues	2026-02-09 09:51:28 +01:00