Skip to content
⌘K
Features
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
workflows
public
Fork
0
Star
0
g1t's reusable workflows, such as .g1t/workflows/deploy.yml.
Overview
Code
Pull requests
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
04226d8f34df221b0782a67a05c8af8bd02080b3
workflows
/
.g1t
syntaqx
Prettier over the repository (Closes
#165
)
04226d8
16h ago
History
..
workflows
..
workflows
A project can build with a workflow. Turning on **Build with a workflow** under Settings, Deployments installs a managed workflow named `g1t` that calls g1t's reusable deploy workflow (`g1t/workflows/.g1t/workflows/deploy.yml@v1`, published from `workflows/` by the actions release) with the project's settings, and pushes and pull requests then start it rather than a build of Deployments' own: the same previews and production, at the same addresses, reported as `g1t / deploy`, now the check of the workflow's job, listed on the Actions page with its runs and logs. A pull request from a fork runs it with a read-only token, as on GitHub, and still gets its preview without the project's build secrets: a read-only job token may open a preview build only from a run of a managed workflow. Fork pull requests run the repository's managed workflows too. Its jobs are Actions time, at cost plus 20% on g1t's machines and free on a self-hosted runner. A workflow named `g1t` in `.g1t/workflows/` takes its place. The deployments and Actions guides say so.
1w ago
