Flyto2 grows through useful examples, small fixes, and honest field reports. This page is the org-wide entry point for all public Flyto2 repositories.
| Need | Best channel |
|---|---|
| Ask how to build a workflow | GitHub Discussions |
| Report a bug | Use the bug template in the repo where it failed |
| Request a feature | Use the feature template and describe the problem first |
| Share a recipe, demo, or integration | Open a Show and Tell discussion |
| Find a first contribution | Start from flyto-core good first issues |
| Report a vulnerability | Follow SECURITY.md, never a public issue |
Good first issues should be concrete, reproducible, and useful without needing private context. Prefer:
- docs examples that clarify a real workflow;
- small recipes that demonstrate one module group;
- broken-link, install, or packaging fixes;
- missing tests for existing behavior;
- focused bug fixes with a minimal reproduction.
Avoid marking issues as good first when they require internal credentials, commercial systems, private roadmaps, or large architecture changes.
Flyto2 is easiest to understand when people can see what it ran. Useful showcases include:
- a YAML recipe for browser automation, data extraction, or reporting;
- before/after screenshots from a replayable workflow;
- an MCP client setup that calls Flyto2 tools;
- a Warroom CE lab with safe sample data;
- a write-up explaining what failed, how it was debugged, and what evidence was captured.
Do not post secrets, customer data, real credentials, private targets, or screenshots that expose third-party accounts.
Maintainers can promote public posts, demos, and releases through the Flyto2 social publishing queue. Each social item should point back to one canonical URL first: a blog post, docs page, landing page, GitHub release, package page, or YouTube demo.
The queue is review-first. Automated posting must stay disabled until the maintainer explicitly provides valid platform credentials at runtime.
- Community and partnerships: hello@flyto2.com
- Security: security@flyto2.com
- Conduct: conduct@flyto2.com