Add GEPRC_TAKER_F405AIO config.h by ot0tot · Pull Request #951 · betaflight/config

ot0tot · 2025-11-07T14:30:08Z

Checklist (✓/✕, or y/n)

Summary by CodeRabbit

New Features
- Added native support for the GEPRC TAKER F405 AIO flight controller.
- Enables onboard accelerometer/gyro, barometer, OSD, and onboard flash for Blackbox logging.
- Preconfigured motor outputs, UART/I2C/SPI, USB detect, inverted beeper, LED strip, and ADC-based current/voltage sensing.
- Includes a user-configured switch for VTX power and sensible defaults for DShot and meter sources for plug-and-fly setup.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2025-11-07T14:30:26Z

Walkthrough

Adds a new board configuration header for GEPRC_TAKER_F405AIO introducing MCU/board/manufacturer IDs, many enabled sensors/peripherals, full pin and timer mappings, peripheral instance selections (ADC/I2C/SPI), device defaults, and numerous macro flags. No other files changed.

Changes

Cohort / File(s)	Summary of changes
New board configuration `configs/GEPRC_TAKER_F405AIO/config.h`	New config header: defines `FC_TARGET_MCU`, `BOARD_NAME`, `MANUFACTURER_ID`; enables sensors/peripherals (ACC, GYRO, BARO, FLASH, MAX7456, etc.); provides full pin map (motors, UARTs, I2C, SPI, ADC, LEDs, beeper, USB detect); declares `TIMER_PIN_MAPPING` and per-channel timer mappings; sets ADC/I2C/SPI/FLASH instances, PINIO/BOX mappings, default blackbox/current/voltage meter sources, DSHOT/beeper polarity, system HSE, and other macro defaults.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Verify TIMER_PIN_MAPPING corresponds to STM32F405 timer channel availability and wiring.
Confirm SPI/I2C instance assignments and CS pins for FLASH, MAX7456, and gyro.
Check ADC channel/pin selections and default current/voltage meter sources.
Validate UART pin assignments, USB detect, PINIO box mappings, and beeper polarity.

Possibly related PRs

Add AXISFLYING ARGUS ECO F4 #780 — Adds a board config header with similar MCU, sensor flags, SPI/I2C/ADC instances, and TIMER_PIN_MAPPING patterns.
Add HGLRCF435_AIO board #884 — Adds a comparable board config header defining matching peripheral macros and pin mappings.

Suggested reviewers

haslinghuis
nerdCopter
blckmn

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description only includes a partial checklist with no explanatory context. Required sections like hardware description, design summary, and testing details are missing entirely.	Provide a comprehensive description including hardware specifications, design overview, relevant details about the GEPRC_TAKER_F405AIO board, and context for the configuration changes. Complete all checklist items or explain unchecked items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a new configuration header for the GEPRC_TAKER_F405AIO flight controller, which matches the new file added in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8c0629a and fb50ded.

📒 Files selected for processing (1)

configs/GEPRC_TAKER_F405AIO/config.h (1 hunks)

🧰 Additional context used

🧠 Learnings (11)

📓 Common learnings

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the BOARD_NAME define in each config.h matches the directory name it resides in (e.g., configs/AXISFLYINGF7AIO/config.h must have #define BOARD_NAME AXISFLYINGF7AIO). This check is required for all Betaflight board configuration reviews.

Learnt from: haslinghuis
Repo: betaflight/config PR: 822
File: configs/AXISFLYINGH7MINI/config.h:29-37
Timestamp: 2025-06-23T18:43:31.746Z
Learning: In Betaflight configuration files, feature enablement macros like USE_MAG are build options that can be controlled at compile time, while hardware instance definitions like MAG_I2C_INSTANCE are predefined in board configurations to assist with hardware mapping when those features are enabled at build time.

Learnt from: haslinghuis
Repo: betaflight/config PR: 656
File: configs/IFLIGHT_F745_AIO/config.h:31-35
Timestamp: 2025-07-28T16:44:59.686Z
Learning: In Betaflight board configurations, when a board design uses the same physical gyro socket but different sensor variants across production batches (e.g., MPU6000 in older batches, ICM42688P in newer batches), the correct approach is to enable both sensor drivers (USE_GYRO_SPI_MPU6000 and USE_GYRO_SPI_ICM42688P) in the same configuration. This allows runtime auto-detection of which sensor is actually present without requiring separate board configurations for each hardware variant.

Learnt from: haslinghuis
Repo: betaflight/config PR: 835
File: configs/HDZERO_HALO_MPU6000/config.h:44-56
Timestamp: 2025-07-14T16:16:56.822Z
Learning: For Betaflight board configurations of boards already in production, pin assignments in config.h files reflect the actual hardware design and cannot be changed, even if they present potential conflicts with debug interfaces. The configuration must match the physical board layout, not ideal software design preferences.

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the `BOARD_NAME` define in config.h files exactly matches the directory name where the config file is located. For example, if the config file is in configs/AXISFLYINGF7AIO/config.h, then the BOARD_NAME should be defined as "AXISFLYINGF7AIO". This ensures proper board identification and configuration loading in Betaflight.

Learnt from: osirisinferi
Repo: betaflight/config PR: 972
File: configs/AXISFLYING_H743PRO/config.h:0-0
Timestamp: 2025-12-03T20:45:27.870Z
Learning: In Betaflight board configurations, always verify that TIMER_PIN_MAP entries do not use the same pin macro name multiple times. Each physical pin should appear only once in the TIMER_PIN_MAP definitions. For example, GYRO_1_CLKIN_PIN and GYRO_2_CLKIN_PIN should each appear exactly once, not have GYRO_1_CLKIN_PIN appear twice. This is a blocking issue that must be resolved before approval.

Learnt from: haslinghuis
Repo: betaflight/config PR: 792
File: configs/BEEROTORF4/config.h:30-30
Timestamp: 2025-05-28T15:42:05.402Z
Learning: The DEFAULT_GYRO_ENABLED macro with both gyros enabled (GYRO_MASK(0) | GYRO_MASK(1)) should only be added to board configurations that have DEFAULT_GYRO_TO_USE set to GYRO_CONFIG_USE_GYRO_BOTH. Boards without this setting should only get the GYRO_COUNT definition to specify the number of available gyros.

Learnt from: haslinghuis
Repo: betaflight/config PR: 792
File: configs/BEEROTORF4/config.h:30-30
Timestamp: 2025-05-28T15:42:05.402Z
Learning: The DEFAULT_GYRO_ENABLED macro with both gyros enabled (GYRO_MASK(0) | GYRO_MASK(1)) should only be added to board configurations that have DEFAULT_GYRO_TO_USE set to GYRO_CONFIG_USE_GYRO_BOTH. Boards without this setting should only get the GYRO_COUNT definition.

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T15:17:30.040Z
Learning: In Betaflight configurations, when a target name suggests dual IMUs (like JHEF7DUAL) but specific hardware variants only have one gyro available, the preferred solution is to use DEFAULT_GYRO_TO_USE macro to specify which gyro to use by default rather than pruning gyro defines or creating redundant configurations. This approach maintains compatibility when the same target is used by multiple hardware variants from the same manufacturer.

Learnt from: haslinghuis
Repo: betaflight/config PR: 814
File: configs/JHEF405PRO/config.h:109-109
Timestamp: 2025-06-08T22:02:28.961Z
Learning: The JHEF405PRO board does not actually use dual gyros despite having GYRO_2_SPI_INSTANCE defined in its configuration. It should not receive GYRO_COUNT or other dual-gyro related definitions since only the first gyro is supported.

📚 Learning: 2025-07-03T04:33:57.480Z

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the BOARD_NAME define in each config.h matches the directory name it resides in (e.g., configs/AXISFLYINGF7AIO/config.h must have #define BOARD_NAME AXISFLYINGF7AIO). This check is required for all Betaflight board configuration reviews.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-06-23T18:43:31.746Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 822
File: configs/AXISFLYINGH7MINI/config.h:29-37
Timestamp: 2025-06-23T18:43:31.746Z
Learning: In Betaflight configuration files, feature enablement macros like USE_MAG are build options that can be controlled at compile time, while hardware instance definitions like MAG_I2C_INSTANCE are predefined in board configurations to assist with hardware mapping when those features are enabled at build time.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-06-02T16:16:20.197Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-06-02T16:16:20.197Z
Learning: In STM32F405-based flight controller configurations, timer pin mappings must be carefully analyzed for DMA stream conflicts, especially between motor timers, LED strip timers, and SPI DMA assignments. Changes to TIMER_PIN_MAPPING should include verification that all required peripherals (motors, LED strip, blackbox SPI) can coexist without DMA conflicts.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-07-14T16:16:56.822Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 835
File: configs/HDZERO_HALO_MPU6000/config.h:44-56
Timestamp: 2025-07-14T16:16:56.822Z
Learning: For Betaflight board configurations of boards already in production, pin assignments in config.h files reflect the actual hardware design and cannot be changed, even if they present potential conflicts with debug interfaces. The configuration must match the physical board layout, not ideal software design preferences.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-12-03T20:45:27.870Z

Learnt from: osirisinferi
Repo: betaflight/config PR: 972
File: configs/AXISFLYING_H743PRO/config.h:0-0
Timestamp: 2025-12-03T20:45:27.870Z
Learning: In Betaflight board configurations, always verify that TIMER_PIN_MAP entries do not use the same pin macro name multiple times. Each physical pin should appear only once in the TIMER_PIN_MAP definitions. For example, GYRO_1_CLKIN_PIN and GYRO_2_CLKIN_PIN should each appear exactly once, not have GYRO_1_CLKIN_PIN appear twice. This is a blocking issue that must be resolved before approval.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-07-03T04:33:57.480Z

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the `BOARD_NAME` define in config.h files exactly matches the directory name where the config file is located. For example, if the config file is in configs/AXISFLYINGF7AIO/config.h, then the BOARD_NAME should be defined as "AXISFLYINGF7AIO". This ensures proper board identification and configuration loading in Betaflight.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-08-28T20:45:36.652Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 888
File: configs/ZEX_ATHENA_MINI/config.h:0-0
Timestamp: 2025-08-28T20:45:36.652Z
Learning: In STM32H743 Betaflight configurations, PA15 maps to TIM2_CH1 (timer index 2) as defined in timer_stm32h7xx.c. When used for GYRO_CLKIN functionality, it's recommended to use the macro name GYRO_1_CLKIN_PIN in TIMER_PIN_MAPPING for consistency with other pin definitions.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-08-20T02:54:58.596Z

Learnt from: ot0tot
Repo: betaflight/config PR: 872
File: configs/HGLRCH743/config.h:82-83
Timestamp: 2025-08-20T02:54:58.596Z
Learning: For Betaflight board configuration reviews, the definitive source for validating UART pin assignments is the serial_uart_{platform}.c file in the Betaflight codebase (e.g., serial_uart_stm32h7xx.c for STM32H7xx platforms), not generic MCU datasheets. These files contain the exact pin mappings that Betaflight supports for each UART peripheral.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-12-03T20:50:01.360Z

Learnt from: osirisinferi
Repo: betaflight/config PR: 972
File: configs/AXISFLYING_H743PRO/config.h:98-98
Timestamp: 2025-12-03T20:50:01.360Z
Learning: In Betaflight board configurations, if PINIOx_BOX or PINIOx_CONFIG defines are present in a config.h file, the corresponding PINIOx_PIN define must also be present to specify the actual pin assignment. Each PINIO instance requires a pin definition before it can be configured or assigned to a box.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

📚 Learning: 2025-08-28T20:45:36.652Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 888
File: configs/ZEX_ATHENA_MINI/config.h:0-0
Timestamp: 2025-08-28T20:45:36.652Z
Learning: In STM32H743 Betaflight configurations, PB0 can use multiple timer options including TIM1_CH2N, TIM3_CH3, and TIM8_CH2N as defined in timer_stm32h7xx.c. For CAMERA_CONTROL_PIN assignments, TIM3_CH3 (timer index 3) is the appropriate choice.

Applied to files:

configs/GEPRC_TAKER_F405AIO/config.h

🔇 Additional comments (3)

configs/GEPRC_TAKER_F405AIO/config.h (3)

26-26: LGTM: BOARD_NAME matches directory name.

The BOARD_NAME correctly matches the directory name configs/GEPRC_TAKER_F405AIO/, ensuring proper board identification.

Based on learnings, this is a required check for all Betaflight board configuration reviews.

116-116: Inconsistency between AI summary and actual code.

The AI-generated summary claims GYRO_1_ALIGN is "defined as a commented option CW180_DEG", but the actual code shows DEFAULT_ALIGN_BOARD_YAW 45 instead. The summary may be outdated or incorrect.

109-109: Fix typo in DEFAULT_VOLTAGE_METER_SOURCE.

The macro value has a typo: VOLATGE_METER_ADC should be VOLTAGE_METER_ADC.

Apply this diff:

-#define DEFAULT_VOLTAGE_METER_SOURCE VOLATGE_METER_ADC
+#define DEFAULT_VOLTAGE_METER_SOURCE VOLTAGE_METER_ADC

⛔ Skipped due to learnings

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-23T13:43:50.456Z
Learning: For Betaflight board configuration reviews, always verify that serial port defines (like ESC_SENSOR_UART, MSP_UART, GPS_UART, etc.) use valid SERIAL_PORT identifiers that match those defined in the Betaflight codebase at src/main/io/serial.h. Common valid identifiers include SERIAL_PORT_USART1, SERIAL_PORT_USART2, SERIAL_PORT_USART3, SERIAL_PORT_UART4, SERIAL_PORT_UART5, etc. Invalid identifiers like SERIAL_PORT_UART3 (should be SERIAL_PORT_USART3) will cause build failures.

Learnt from: osirisinferi
Repo: betaflight/config PR: 972
File: configs/AXISFLYING_H743PRO/config.h:0-0
Timestamp: 2025-12-03T20:45:27.870Z
Learning: In Betaflight board configurations, always verify that TIMER_PIN_MAP entries do not use the same pin macro name multiple times. Each physical pin should appear only once in the TIMER_PIN_MAP definitions. For example, GYRO_1_CLKIN_PIN and GYRO_2_CLKIN_PIN should each appear exactly once, not have GYRO_1_CLKIN_PIN appear twice. This is a blocking issue that must be resolved before approval.

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-23T13:43:50.456Z
Learning: For Betaflight board configuration reviews, always verify that serial port defines use valid identifiers from the serialPortIdentifier_e enum in src/main/io/serial.h. Valid identifiers include: SERIAL_PORT_USB_VCP (20), SERIAL_PORT_SOFTSERIAL1 (30), SERIAL_PORT_SOFTSERIAL2 (31), SERIAL_PORT_LPUART1 (40), SERIAL_PORT_UART0 (50, if SERIAL_UART_FIRST_INDEX == 0), SERIAL_PORT_USART1 (51 or 50), SERIAL_PORT_USART2, SERIAL_PORT_USART3, SERIAL_PORT_UART4, SERIAL_PORT_UART5, SERIAL_PORT_USART6, SERIAL_PORT_USART7, SERIAL_PORT_USART8, SERIAL_PORT_UART9, SERIAL_PORT_USART10. While some aliases exist (like SERIAL_PORT_UART3 = SERIAL_PORT_USART3), prefer using the primary identifiers as referenced in the serialPortIdentifiers array to avoid build failures.

Learnt from: osirisinferi
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-09-26T16:32:46.694Z
Learning: When reviewing hardware configuration files like Betaflight configs, always check for pin assignment conflicts by verifying that no physical pins (like PB10, PB11, etc.) are assigned to multiple peripheral functions simultaneously.

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the BOARD_NAME define in each config.h matches the directory name it resides in (e.g., configs/AXISFLYINGF7AIO/config.h must have #define BOARD_NAME AXISFLYINGF7AIO). This check is required for all Betaflight board configuration reviews.

Learnt from: ot0tot
Repo: betaflight/config PR: 872
File: configs/HGLRCH743/config.h:82-83
Timestamp: 2025-08-20T02:54:58.596Z
Learning: For Betaflight board configuration reviews, the definitive source for validating UART pin assignments is the serial_uart_{platform}.c file in the Betaflight codebase (e.g., serial_uart_stm32h7xx.c for STM32H7xx platforms), not generic MCU datasheets. These files contain the exact pin mappings that Betaflight supports for each UART peripheral.

Learnt from: haslinghuis
Repo: betaflight/config PR: 835
File: configs/HDZERO_HALO_MPU6000/config.h:44-56
Timestamp: 2025-07-14T16:16:56.822Z
Learning: For Betaflight board configurations of boards already in production, pin assignments in config.h files reflect the actual hardware design and cannot be changed, even if they present potential conflicts with debug interfaces. The configuration must match the physical board layout, not ideal software design preferences.

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-06-02T16:16:20.197Z
Learning: For Betaflight configurations, blackbox logging via SPI3 and LED_STRIP functionality can be mutually exclusive due to DMA stream conflicts on STM32F4 targets. This hardware limitation should be identified during timer configuration reviews.

Learnt from: haslinghuis
Repo: betaflight/config PR: 822
File: configs/AXISFLYINGH7MINI/config.h:29-37
Timestamp: 2025-06-23T18:43:31.746Z
Learning: In Betaflight configuration files, feature enablement macros like USE_MAG are build options that can be controlled at compile time, while hardware instance definitions like MAG_I2C_INSTANCE are predefined in board configurations to assist with hardware mapping when those features are enabled at build time.

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-06-02T16:16:20.197Z
Learning: In STM32F405-based flight controller configurations, timer pin mappings must be carefully analyzed for DMA stream conflicts, especially between motor timers, LED strip timers, and SPI DMA assignments. Changes to TIMER_PIN_MAPPING should include verification that all required peripherals (motors, LED strip, blackbox SPI) can coexist without DMA conflicts.

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.}

configs/GEPRC_TAKER_F405AIO/config.h

pitts-mo · 2025-12-14T15:36:36Z

Pins and timers for Motors 3 and 4 are not correct.

Minimal CLI changes needed after full erase flash of GepRC_Taker_F405AIO are:
resource MOTOR 3 C08
resource MOTOR 4 C09
timer C08 AF3
timer C09 AF3
dma pin C08 1
dma pin C09 0

I suspect these changes are needed but declined submit after seeing the PR template :-)
master...pitts-mo:config:patch-1

* Add GEPRC_TAKER_F405AIO config.h * Fix gyro alignment * Add default on-board receiver

Greypang · 2026-01-22T07:03:49Z

Thank you for your feedback，We will resubmit a new PR to resolve the issue

Add GEPRC_TAKER_F405AIO config.h

8c0629a

coderabbitai bot approved these changes Nov 7, 2025

View reviewed changes

haslinghuis assigned ot0tot Nov 7, 2025

haslinghuis approved these changes Nov 7, 2025

View reviewed changes

configs/GEPRC_TAKER_F405AIO/config.h Outdated Show resolved Hide resolved

haslinghuis added Awaiting Prototype Samples Awaiting prototype samples Schematics Approved Uses Betaflight Connector Standard labels Nov 7, 2025

ot0tot added 2 commits December 5, 2025 02:33

Fix gyro alignment

491e6fc

Add default on-board receiver

fb50ded

ot0tot requested review from nerdCopter and sugaarK December 5, 2025 07:48

nerdCopter approved these changes Dec 5, 2025

View reviewed changes

haslinghuis merged commit 96002a1 into betaflight:master Dec 5, 2025
2 checks passed

coderabbitai bot mentioned this pull request Dec 14, 2025

GepRC_Taker_F405AIO -fix motor pins and timers #982

Closed

lukas-principiot pushed a commit to PrincipIoT/config that referenced this pull request Dec 27, 2025

Add GEPRC_TAKER_F405AIO config.h (betaflight#951)

e514b61

* Add GEPRC_TAKER_F405AIO config.h * Fix gyro alignment * Add default on-board receiver

This was referenced Dec 29, 2025

Add HGLRC_F405_S board #987

Merged

AKINGF405HD #999

Closed

coderabbitai bot mentioned this pull request Jan 7, 2026

Add SIMPLIFLYF405 #1003

Merged

This was referenced Jan 21, 2026

Add RUSH BLADEF4 from unified-targets #1014

Merged

Update M3 M4 motor settings #1017

Merged

coderabbitai bot mentioned this pull request Feb 3, 2026

Add configuration file for AKINGF405HD #1023

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add GEPRC_TAKER_F405AIO config.h#951

Add GEPRC_TAKER_F405AIO config.h#951
haslinghuis merged 3 commits intobetaflight:masterfrom
ot0tot:Add-GEPRC-TAKER-F405-AIO

ot0tot commented Nov 7, 2025 •

edited

Loading

Uh oh!

coderabbitai bot commented Nov 7, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

pitts-mo commented Dec 14, 2025 •

edited

Loading

Uh oh!

Greypang commented Jan 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

ot0tot commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested reviewers

Pre-merge checks and finishing touches

Uh oh!

Uh oh!

Uh oh!

pitts-mo commented Dec 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Greypang commented Jan 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ot0tot commented Nov 7, 2025 •

edited

Loading

coderabbitai bot commented Nov 7, 2025 •

edited

Loading

pitts-mo commented Dec 14, 2025 •

edited

Loading