joseph-sentry

> So I'd opt to make the CLI send specific headers with the information we need. (Also by removing the current checks maybe X-Tokenless-PR header is useless?) We could just...

> what is matrix doing here? Or rather, what's the point and what does it help do? @thomasrockhu-codecov the idea is that the action would pass the `strategy.matrix` converted to...

> @joseph-sentry is this specific to test-results? or will coverage need it too? I think this only makes sense for test results right now, but in the future we could...

> @joseph-sentry I think we should also have it run on prod as well as staging I wasn't actually planning on making this an actual PR, I was just testing...

Hi @ccadar, it seems this is a documentation mishap, it's true that in the UI those bars would show up as yellow as soon as it's above the range. The...

> At least from the examples and argument documentation, it's not clear how to do this. Perhaps something like files: test-output/*.junit.xml would work? @jluebbe you are correct, it is missing...

> Pretty easy. What caught me off guard was the naming convention enforcing file names ending on *junit.xml. That could either be mentioned more visibly or loosend. @Bibo-Joshi this restriction...

@thomasrockhu-codecov since we made the API changes for the new tokenless, unless a user is using the updated CLI (which hasn't been released yet) and the updated action, tokenless won't...

Hi all, indeed tokenless uploads were broken for v0.7.0 of the CLI, we just released v0.7.1 which should fix that bug. If you've already versioned to v0.6.0, that should work...

Here's what I found: - [link](https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd) this spec doesn't even include the field - [link](https://github.com/testmoapp/junitxml) this spec defines it as "the name of the entire test run" - [link](https://www.ibm.com/docs/en/developer-for-zos/14.2?topic=formats-junit-xml-format) this...