Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
Pull requests
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
0cf07af282dc2b1625a9d0424c50f75df3570ce9
g1t
/
…
/
crates
/
actions
/
src
Claude
agent
Merge branch 'worktree-agent-a641fa0e2e4fffccb' into claude/cool-newton-7nm8r9
0cf07af
1d ago
History
..
cron.rs
events.rs
expr.rs
filter.rs
lib.rs
managed.rs
mask.rs
matrix.rs
permissions.rs
syntax.rs
workflow.rs
..
cron.rs
Merge branch 'worktree-agent-ab9543c492a7ed481' into spend-guardrails
4d ago
events.rs
What 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.
1d ago
expr.rs
Fast pages, required checks on the branch, self-hosted runners, honest incidents
6d ago
filter.rs
GitHub Actions on g1t, part one: reading workflows
10d ago
lib.rs
Merge branch 'worktree-agent-a641fa0e2e4fffccb' into claude/cool-newton-7nm8r9
1d ago
managed.rs
A repository can run a managed workflow: one installed by g1t's own services without a file in the repository. It is listed, started, run and re-run like any workflow in `.g1t/workflows/`, under the path `managed/<name>.yml`, and a workflow of the same `name:` in the repository runs in its place, so moving one into the repository is committing its source. The Actions page says a managed workflow is managed by g1t rather than linking to a file. Nothing installs one yet; the deploy workflow deployments will install, which calls g1t's reusable deploy workflow with a project's settings as its inputs and reports as `g1t / deploy`, is written and tested but not installed.
1d ago
mask.rs
Merge branch 'worktree-agent-a3abfcce648e87dca'
4d ago
matrix.rs
GitHub Actions on g1t, part one: reading workflows
10d ago
permissions.rs
Repository listing follows a fine-grained token's selection; job tokens never get workflow files
4d ago
syntax.rs
Merge branch 'worktree-agent-a641fa0e2e4fffccb' into claude/cool-newton-7nm8r9
1d ago
workflow.rs
Merge branch 'worktree-agent-a641fa0e2e4fffccb' into claude/cool-newton-7nm8r9
1d ago