The shared community resources for Florex Labs: contribution guides, support and security policies, issue templates, and the organization profile.

Looking for our tools? Visit the public profile or browse the public repositories.

GitHub uses supported community files from this public .github repository when a repository in the organization does not provide its own. This applies regardless of the destination repository's visibility. Existing repository files take precedence; the defaults are not copied into its Git history.

If a repository defines its own issue templates or template configuration, GitHub uses that set instead of merging it with these defaults.

Licenses, workflows, labels, and repository settings require separate setup. The MIT license covers this repository; check each project's own license for its terms. The root FUNDING.yml is a reference file; GitHub requires funding configuration in .github/FUNDING.yml to use it as a default.

See GitHub's default community file documentation for supported files and placement rules.

• Edit profile/README.md to update the organization profile.
• Feature only public repositories, and confirm their visibility before adding links.
• Keep project descriptions specific and avoid naming private projects or internal systems.
• Update shared policies here; use repository-specific files for exceptions.
• Check relative links and labels whenever templates change.

Before changing the public profile, verify the current repository inventory:

gh repo list florextech --limit 500 --json name,visibility,url

• Community file precedence
• Engineering standards
• Adoption guide
• Adoption script

The adoption script can change labels, licenses, and settings across the organization. Review the guide and preview the intended task before running it:

./scripts/adopt-org-defaults.sh labels --dry-run

florexlabs.com · [email protected]