Skip to content

Rename smix max to fixed#2631

Open
sensei-hacker wants to merge 1 commit into
iNavFlight:maintenance-9.xfrom
sensei-hacker:rename_smix_max_to_fixed
Open

Rename smix max to fixed#2631
sensei-hacker wants to merge 1 commit into
iNavFlight:maintenance-9.xfrom
sensei-hacker:rename_smix_max_to_fixed

Conversation

@sensei-hacker
Copy link
Copy Markdown
Member

To set a fixed value in the servo mixer, previously one had to choose "MAX" as the source. That's misleading because it's not always the max value. This PR renames it to "fixed value".

@qodo-code-review
Copy link
Copy Markdown
Contributor

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@github-actions
Copy link
Copy Markdown

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

  • maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

  • maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change because it should never be included in any release, no action is needed.


This is an automated suggestion to help route contributions to the appropriate branch.

@sensei-hacker sensei-hacker changed the base branch from master to maintenance-9.x May 24, 2026 16:54
@sonarqubecloud
Copy link
Copy Markdown

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant