-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup doxygen doc #42
Conversation
Ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. Maybe we wait for Sphinx first ?
I don't know, conflicts guaranteed in both cases, so waiting for #26. |
Some commits have to be squashed. |
b5714fa
to
11ba284
Compare
ec1bfd6
to
0908561
Compare
Ready for the merge. |
@hiergaut this branch has conflicts and cannot be rebased, can you have a look please ? |
Sure |
38bd098
to
e7659c3
Compare
e7659c3
to
b5eecd8
Compare
@nmellado done |
Pull Request Desription
Check if you branch history is PR compatible
git fetch origin
if origin is this remotescripts/source-format-all.sh
These checks are enforced by github workflow actions
Please refer to the corresponding log in case of failure
UPDATE the form below to describe your PR
Please check if the PR fulfills these requirements
Be aware that the PR request cannot be accepted if it doesn't pass the Continuous Integration tests.
What kind of change does this PR introduce?
What is the current behavior? (You can also link to an open issue here)
Doxygen has empty comments.
What is the new behavior (if this is a feature change)?
Doxygen has useful comments.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
Only documentation performed.