Skip to content

Manufacturers: Add Coolfly (CFLY) to the list#1031

Open
redstonee wants to merge 1 commit intobetaflight:masterfrom
redstonee:add-kt-fmu-f1
Open

Manufacturers: Add Coolfly (CFLY) to the list#1031
redstonee wants to merge 1 commit intobetaflight:masterfrom
redstonee:add-kt-fmu-f1

Conversation

@redstonee
Copy link
Copy Markdown

@redstonee redstonee commented Feb 19, 2026

Checklist (✓/✕, or y/n)

  • [ n ] passed Betaflight team's schematics review
  • [ n ] passed hardware samples testing
  • [ y ] follows guidelines
  • [ n ] follows connector standards
  • [ y ] flight tested
  • [ n ] comments/issues resolved

Summary by CodeRabbit

  • Documentation
    • Added a new manufacturer entry for CFLY (Coolfly (Xiamen) Co., Ltd) to the manufacturer listings.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 19, 2026

Caution

Review failed

Failed to post review comments

Walkthrough

A single manufacturer entry (CFLY - Coolfly (Xiamen) Co., Ltd) has been added to the Manufacturers.md table at a specific position in the alphabetical listing.

Changes

Cohort / File(s) Summary
Manufacturer Registry
Manufacturers.md
Added new manufacturer entry CFLY (Coolfly (Xiamen) Co., Ltd) with corresponding URL to the manufacturers table.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

New manufacturer, Housekeeping

Suggested reviewers

  • ot0tot
  • nerdCopter
  • haslinghuis
🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description is entirely boilerplate template text with no customization. The instruction 'Replace this text with details of your own' was not followed, and no checklist items are checked despite adding a new manufacturer entry. Replace the template boilerplate with actual PR details about the Coolfly manufacturer addition, complete the checklist items, and specify which flight controllers or hardware releases are included.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Manufactrurers: Add Coolfly (CFLY) to the list' clearly summarizes the main change—adding a new manufacturer entry to the list, matching the changeset content.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@redstonee
Copy link
Copy Markdown
Author

PR description updated

@haslinghuis haslinghuis changed the title Manufactrurers: Add Coolfly (CFLY) to the list Manufacturers: Add Coolfly (CFLY) to the list Feb 19, 2026
@ot0tot
Copy link
Copy Markdown
Contributor

ot0tot commented Feb 19, 2026

Do you have a FC design under review? There is no need to add the manufacturer ID until you have an approved target.

@redstonee
Copy link
Copy Markdown
Author

Yes, I'm debugging it these days. It will probably be done in a few days.

@ot0tot
Copy link
Copy Markdown
Contributor

ot0tot commented Feb 20, 2026

Yes, I'm debugging it these days. It will probably be done in a few days.

Debugging what? You should not create hardware until the schematic has passed initial review.

@redstonee
Copy link
Copy Markdown
Author

redstonee commented Feb 20, 2026

Well, the board has already been assembled and is running other firmware 😥
I'll upload the schematic then

@sugaarK
Copy link
Copy Markdown
Member

sugaarK commented Feb 24, 2026

Well, the board has already been assembled and is running other firmware 😥 I'll upload the schematic then

if you want it to run our firmware it has to meet our standards

@redstonee
Copy link
Copy Markdown
Author

I see. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

New Manufacturer Add manufacturer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants