Add FlyMod back to manufacturer list

[haslinghuis]

Summary by CodeRabbit

• Documentation
  • Updated the manufacturers list to include FlyMod (ID: FLMO) with a link (https://flymod.net/). The new entry is inserted between Flying Lemon FPV (FLLF) and FlightOne (FLON). No existing entries were removed or changed; the public manufacturers table now lists the additional vendor.

[coderabbitai]

Walkthrough

Added a new manufacturer entry FLMO | FlyMod | https://flymod.net/ to Manufacturers.md, inserted between FLLF and FLON. No deletions or other public API changes.

Changes

Cohort / File(s)	Summary of Changes
Docs: Manufacturers list Manufacturers.md	Inserted a new table row for manufacturer FLMO (FlyMod) with URL https://flymod.net/, placed between FLLF and FLON.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add Warp Labs (WPRL) to Manufacturers #844 — Adds a manufacturer row to Manufacturers.md; similar modification to the same list.
• feat(config): update and sort manufacturers list #874 — Also inserts the FLMO (FlyMod) entry into Manufacturers.md.

Suggested labels

New manufacturer

Suggested reviewers

• ot0tot
• nerdCopter
• sugaarK

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 784d5f0 and 4e2972e.

📒 Files selected for processing (1)

• Manufacturers.md (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📚 Learning: 2025-07-14T15:47:16.394Z

Learnt from: ot0tot
PR: betaflight/config#681
File: configs/NYX405V1/config.h:26-28
Timestamp: 2025-07-14T15:47:16.394Z
Learning: In Betaflight configuration files, MANUFACTURER_ID values must be exactly 4 ASCII characters long, not 3 characters. All manufacturer IDs in the codebase consistently use 4-character identifiers like AIRB, FOSS, SPBE, MTKS, NERC, etc.

Applied to files:

• Manufacturers.md

📚 Learning: 2025-08-14T17:46:20.018Z

Learnt from: haslinghuis
PR: betaflight/config#863
File: Manufacturers.md:116-116
Timestamp: 2025-08-14T17:46:20.018Z
Learning: In Betaflight's Manufacturers.md file, all URLs are formatted as bare URLs without angle brackets. This is the consistent pattern used throughout the entire table with 92 bare URLs and 0 wrapped URLs.

Applied to files:

• Manufacturers.md

📚 Learning: 2025-08-14T17:46:20.018Z

Learnt from: haslinghuis
PR: betaflight/config#863
File: Manufacturers.md:116-116
Timestamp: 2025-08-14T17:46:20.018Z
Learning: In Betaflight's Manufacturers.md file, company name formatting with "Co." shows variation: "Co., Ltd." (6 times) is most common, followed by "Co., LTD" and "Co., Ltd" (3 times each), while "Co.,Ltd." without space after comma appears only once.

Applied to files:

• Manufacturers.md

🪛 markdownlint-cli2 (0.17.2)

Manufacturers.md

57-57: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)

Manufacturers.md (1)

57-59: LGTM: Manufacturer table update is correct.

• FLMO is a valid 4-character ASCII ID.
• The new row sits in proper alphabetical order within the FL* block (after FLLF and before FLON).
• No duplicate IDs detected across the entire table.
• URL style matches the existing bare-URL convention (MD034 is intentionally suppressed).

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch haslinghuis-patch-6

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary or `` to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

Manufacturers.md (1)

1-146: Fix alphabetical ordering in Manufacturers.md

The validation script identified three out-of-order entries. Please reorder them as follows:

• COMM (line 10) should appear before FOSS
• AEDR (line 12) should appear before LEGA
• FLMO (line 59) should appear before FLTE

No duplicate Manufacturer Ids were found.

🧹 Nitpick comments (1)

Manufacturers.md (1)

59-59: markdownlint MD034 warning: bare URL.

The linter flags bare URLs. The file mostly uses bare URLs, so keep as-is for consistency or wrap all contact URLs repo-wide in a follow-up. If you prefer to satisfy MD034 on this line now:

Optional one-line change:

-|FLMO|FlyMod|https://flymod.net/|
+|FLMO|FlyMod|<https://flymod.net/>|

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 0e15f75 and 784d5f0.

📒 Files selected for processing (1)

• Manufacturers.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

Manufacturers.md

59-59: Bare URL used

(MD034, no-bare-urls)