How to document actionlib interface / Best practice for messages from .action files
I want to document the action interface in nao_driver which uses custom actions defined in nao_msgs. However, the messages themselves are generated from the .action files and this does not seem to happen when the wiki documentation is built. As a result, the message links in the node documentation point to nonexistent pages and there are no actions visible at nao_msgs in the MsgSrvDoc macro block. How should I document the interface? Is it considered "best practice" to check in the generated msgs from the .action files? I don't like the fact that this could cause a new checkin every time they are regenerated.