Please use a separate commit (which isn't being squashed when merging later) to rename existing files (instead of deleting one and creating another with very similar content).

Please use a separate commit to rename existing files

Hmm, it is true that the two current tests were based upon an existing one that was later deleted. But this isn't pure renaming, the original test was split in two. Would you rather have the original test renamed to one of the current ones?

I just want the history to be preserved. If you want to use a different filename then you should rename the file in a separate commit without making any changes to it. Follow up commits can then change the content in any way.

Done, sorry about the force push. Github's UI shows the original file as deleted though.

The blame view can now track changes from the past: https://github.com/ros2/ros1_bridge/blame/a96ee952c63c0975887c09057b1b6e062c881951/test/test_topics_across_dynamic_bridge.py.in

Looking at the diff now it seems that the service file is also derived from the original file (I though it was a new addition). In that case it would be good to copy the file after renaming it and before making the changes - again to be able to track the changes of the content.

Done @dirk-thomas !

@jacobperron @dirk-thomas mind to approve with powers? @ivanpauno lacks them.