Lucas Brendel

It would be nice to carry over the behavior of [cargo-travis](https://github.com/roblabla/cargo-travis) for code coverage as well as documentation publishing to gh-pages

@svartalf i totally get not wanting to duplicate work. So would #2 and #3 cover creating coverage reports for something like codecov and then use the codecov action to upload?...

One thing I have started looking at and I realize I am edge case, is I have been using the full names for units, because I just see it easier...

I recently did some investigating and replacing all use of the `LFS_MKATTRS` macro with the actual code by assigning it to a variable and then placing it where the macro...

I could do an experiment to see, removing the warning. The bigger problem is the last line in the original post `ctc S900: internal consistency check failed - please report`...