iptc
Here are 50 public repositories matching this topic...
-
Updated
Nov 18, 2020 - C#
-
Updated
Nov 24, 2020 - Python
-
Updated
Nov 19, 2020 - Go
We used to have this (tracked in felixc/rexiv2#18, set up in felixc/rexiv2@90ae678), but it had to be removed in felixc/rexiv2@1aff63e because the travis-cargo project we'd been using had broken ages ago was no longer actually uploading coverage info.
-
Updated
Sep 23, 2020 - Go
-
Updated
Oct 1, 2020 - Python
-
Updated
Mar 14, 2019 - C++
-
Updated
Dec 3, 2020 - JavaScript
-
Updated
Apr 2, 2020 - PHP
-
Updated
Nov 3, 2017 - JavaScript
-
Updated
May 21, 2018 - PHP
-
Updated
Dec 2, 2020 - Python
-
Updated
May 2, 2017 - Python
-
Updated
Nov 22, 2020 - JavaScript
-
Updated
Jun 15, 2020 - Dockerfile
-
Updated
Oct 19, 2020 - Shell
-
Updated
Jan 30, 2020 - Java
Improve this page
Add a description, image, and links to the iptc topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the iptc topic, visit your repo's landing page and select "manage topics."
Although we already have an option in CMake which add the needed compiler flags in GCC and CLANG to produce coverage information (this is used by the tools we employ in the PRs to generate coverage reports) it would be nice to also add some targets in the CMake configuration to generate local coverage reports.
This would be useful for exploring not exercised paths in the code while testing eit