Skip to content

global/build-in-public

Build in Public — turn GitHub repo activity into authentic developer storytelling posts.

Category: global
Source: workflows/content/build_in_public.py

FieldTypeDefaultDescription
author_contextstring""
author_namestring""
github_ownerstring""
github_repostring""
github_tokenobject
num_postsinteger5
platformsstring"twitter,linkedin,threads,tiktok,youtube"
regenerateobjectWhen set, this run is a regeneration. Workflows may read direction / keep / extra_instructions to modulate prompts; the engine persists parent_run_id and parent_variant_index as run lineage columns.
repo_urlstring""
time_range_daysinteger30
variantsinteger1Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs.
voicestring"conversational"

No schema defined.

validate_input → fetch_readme → fetch_releases → fetch_commits → merge_github_data → extract_story_angles → generate_bip_posts → quality_gate_authenticity → bridge_to_platform_texts → validate_and_refine → format_output
TaskDescription
validate_inputParse the GitHub repo URL and merge user config with defaults.
fetch_readmeFetch the repository README via GitHub Contents API.
fetch_releasesFetch recent releases (or tags as fallback) from GitHub.
fetch_commitsFetch recent commits from GitHub.
merge_github_dataMerge parallel GitHub fetch branches into unified context.
extract_story_anglesFind human stories buried in repo data using BIP archetype vocabulary.
generate_bip_postsGenerate platform-native build-in-public posts from story angles.
quality_gate_authenticityScore posts on BIP authenticity in batches to keep LLM output manageable.
bridge_to_platform_textsReshape bip_posts into the platform_texts schema for validate_and_refine.
validate_and_refineValidate generated posts against platform constraints and iteratively refine.
format_outputStructure the final output, stripping internal keys.

Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.

workflow: global/build-in-public
# Optional fields — copy any line(s) under `input:` and uncomment to set:
# author_context: ""
#
# author_name: ""
#
# github_owner: ""
#
# github_repo: ""
#
# github_token: null
#
# num_posts: 5
#
# platforms: "twitter,linkedin,threads,tiktok,youtube"
#
# repo_url: ""
#
# time_range_days: 30
#
# voice: conversational
#
input: {}

Run it locally:

Terminal window
fab-workflow --from-file my-run.yaml

Or submit over the wire — the same file is the request body:

Terminal window
curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=global/build-in-public' \
-H 'Authorization: Bearer fab_xxx' \
-H 'content-type: application/yaml' \
--data-binary @my-run.yaml

Every workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).

  • Last user task format_output has no Pydantic return type — workflow output schema is null. Declare a WorkflowOutput subclass and pass it to Flow(output=…) for a strict contract.
  • Task merge_github_data has no Pydantic types — contract is opaque to consumers.