add target FOXAIR722

[xinshou249]

Important considerations when opening a pull request:

1. For all pull requests that add or update a Unified Target configuration, please read and follow these instructions.

2. Make sure you do not make the changes you want to open a pull request for on the master branch of your fork, or open the pull request from the master branch of your fork. Some of our integrations will fail if you do this, resulting in your pull request not being accepted. If this is your first pull request, it is probably a good idea to first read up on how opening pull requests work (https://opensource.com/article/19/7/create-pull-request-github is a good introduction);

3. Pull requests will only be accepted if they are opened against the master branch of our repository. Pull requests opened against other branches without prior consent from the maintainers will be closed;

4. Please follow the coding style guidelines: https://github.com/betaflight/betaflight/blob/master/docs/development/CodingStyle.md

5. Keep your pull requests as small and concise as possible. One pull request should only ever add / update one feature. If the change that you are proposing has a wider scope, consider splitting it over multiple pull requests. In particular, pull requests that combine changes to features and one or more new targets are not acceptable.

6. Ideally, a pull request should contain only one commit, with a descriptive message. If your changes use more than one commit, rebase / squash them into one commit before submitting a pull request. If you need to amend your pull request, make sure that the additional commit has a descriptive message, or - even better - use git commit --amend to amend your original commit.

7. All pull requests are reviewed. Be ready to receive constructive criticism, and to learn and improve your coding style. Also, be ready to clarify anything that isn't already sufficiently explained in the code and text of the pull request, and to defend your ideas.

8. We use continuous integration (CI) with Travis to build all targets and run the test suite for every pull request. Pull requests that fail any of the builds or fail tests will most likely not be reviewed before they are fixed to build successfully and pass the tests. In order to get a quick idea if there are things that need fixing before opening a pull request or pushing an update into an existing pull request, run make pre-push to run a representative subset of the CI build. Note: This is not an exhaustive test (which will take hours to run on any desktop type system), so even if this passes the CI build might still fail.

9. If your pull request is a fix for one or more issues that are open in GitHub, add a comment to your pull request, and add the issue numbers of the issues that are fixed in the form Fixes #<issue number>. This will cause the issues to be closed when the pull request is merged;

10. Remove this Text :).

[haslinghuis]

• Please stop adding PR's and closing them to make changes. Learn how to use git as changes can be made in same PR.
• There is no FOXAIR manufacturer.

[xinshou249]

I‘m so sorry! Since there were no changes, I chose to re PR instead of making modifications on it.
I am a new manufacturer.Do I need to contact you on Discord first?

[nerdCopter]

1 branch, 1 PR. set draft until ready. modify/push branch until final result. set ready for review.

[xinshou249]

What should I do now? Close this PR？

[nerdCopter]

What should I do now? Close this PR？

no, keep this one open. i was simply responding that multiple PR open/closures for the same thing was not good workflow.

i think you know what to do now for future events.

[haslinghuis]

@xinshou249 For the manufacturer ID we need

• 4 characters for ID
• company name
• website with product information
• contact information