A community
Tools for hatching new Flutters. Nest is the tooling project behind Flock, and flutterfoundation.dev is its official web home.
Nest brings together scripts and workflows for assembling and maintaining a Flutter fork. Its public source includes fork assembly, engine builds, repository publication and test workflows. The existence of a workflow does not establish that its latest run succeeded or that every target has a usable release.
Read before running
Identify the source
Open the Nest repository and record a revision. Read its README and the workflow you intend to use.
Map inputs and outputs
Identify the upstream revision, patch inventory, engine targets and artifact destinations. Avoid providing credentials until you understand what an operation publishes.
Choose an isolated test
Prepare a separate workspace and a rollback route. Compare the same target against a known baseline; retain the actual commands and results.
Begin with the maintenance map, then read the original contributor setup and patch workflow.
Sources & further reading
Go deeper on this task
- Read Nest’s assembly and publication workflows
Follow the checked Nest source from trigger through assembly to remote publication, without confusing configuration with a successful run.
- Trace a Nest engine artifact to its build inputs
Read the engine workflow’s target matrix, revision identifiers and artifact destinations before trusting a binary.
- Review an upstream conflict before editing a patch
A review worksheet for distinguishing a text conflict from a changed behavioural requirement in a Flutter fork.
Resolve the next specific question
- Read a Nest patch manifest before replaying it
Inspect order, files, source-defined arguments and checkout identity without changing Git history.