chore: update md

[PengBoUESTC]

update introduction of analyzerPort option

[linux-foundation-easycla[bot]]

• :white_check_mark: login: valscion / name: Vesa Laakso (44622ff567db00bf583eb38a22bb24691715dda3)
• :x: The commit (84d4c1593eb70c49de7a7a41868e0e302e65700e, 48fce54315ce469c886eeeaa8a73031d7aa0c9b7). This user is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve.For further assistance with EasyCLA, please submit a support request ticket.

[valscion]

Thanks, looks good to me! Can you sign the CLA?

[PengBoUESTC]

/check-cla

[valscion]

Looks like your original commit used some email that isn't tied to your GitHub account so GitHub and thus EasyCLA isn't able to link them together.

https://docs.github.com/en/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user

[PengBoUESTC]

Looks like your original commit used some email that isn't tied to your GitHub account so GitHub and thus EasyCLA isn't able to link them together.

https://docs.github.com/en/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user

I register CLA just now, how to deal with that

[valscion]

If you've configured your local git client now properly then the easiest way to solve this might be to start fresh with a new pull request and new commits.

[valscion]

I retriggered the CLA authorization but it didn't pass