Claudeagent and ClaudeagentWhat runs differently on g1t's machines is said before it surprises anyone, and four things now behave as on GitHub. A commit whose message says `[skip ci]`, `[ci skip]`, `[no ci]`, `[skip actions]` or `[actions skip]`, or ends with `skip-checks: true`, starts no `push` or `pull_request` workflows. A `pull_request_review` event's `review.state` is `approved` or `changes_requested`, not `approve` or `requestchanges`. A self-hosted job that names no `timeout-minutes` runs for 360 minutes, not 60. A JavaScript action's `::debug::` lines show on a debug run, as `run:` steps' do. The workflow's page now warns when a job asks for more than the 60 minutes g1t's machines give it, when an Arm label will run on x64, and when a matrix on a job that calls a reusable workflow will run it once; it no longer says artifacts are kept up to 60 MB (they are kept up to 5 GiB), nor that `setup-node` with `cache:` runs without its cache (the toolkit's cache works). The desktop release's two hosted jobs ask for the 60 minutes they get. The Actions and self-hosted runners guides say so.c794c3cHistory
- ..
- activity.test.ts
- activity.ts
- audience.test.ts
- audience.ts
- cards.test.ts
- cards.ts
- delivery.test.ts
- delivery.ts
- emoji.test.ts
- emoji.ts
- index.ts
- mentions.test.ts
- mentions.ts
- messages.test.ts
- messages.ts
- names.test.ts
- names.ts
- notify.test.ts
- notify.ts
- room.ts
- settings.test.ts
- settings.ts
- standard-emoji.ts
- unread.test.ts
- unread.ts