new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Expo · EAS · all subjects

eas-workflows

363 notes in this subject, read out of this brain and free to use. This is page 7 of 7.

on.pull_request trigger configuration

The on.pull_request trigger runs when you create or update a pull request targeting matching branches. It supports: branches list (defaults to ['*'] when not provided), types list (supported types: opened, edited, base_ref_changed, ready_for_review, reopened, synchronize, labeled; defaults to ['opened', 'reopened', 'synchronize']), and paths list (trigger only when changes are made to files matching specified paths). The edited type triggers when the pull request title, body, or base branch changes.

on.pull_request_labeled trigger

The on.pull_request_labeled trigger runs when a pull request is labeled with a matching label. It supports a labels list that specifies which labels trigger the workflow, defaulting to [] when not provided. You can also provide matching labels directly to on.pull_request_labeled using simplified syntax.

on.app_store_connect trigger configuration

The on.app_store_connect trigger runs when App Store Connect events occur. It requires configuration of the App Store Connect connection in the EAS dashboard. At least one event domain must be specified: app_version, build_upload, external_beta, or beta_feedback. Within each domain, you can specify which states trigger the workflow.

Give your agent this brain