-
Notifications
You must be signed in to change notification settings - Fork 16
setup help #22
Comments
do you have a repro build? |
Can you try with version 1.1.0? |
tried with 1.10
I'm using it from a private repository, not sure if that matters. |
This is running in a PR from a fork. I setup a GitHub token and get a different error
My repository is a mix of Rust and C# on the rust side I run |
From the readme, it seems the entire motivation for actions-rs/clippy was to replace clippy-check so that it would not require GITHUB_TOKEN and it would work on prs from forks. I'll check how they do that. |
Ok, I implemented the same hack they did, can you try this branch before I merge it? like this: - uses: MirageNet/nunit-reporter@accesscode
if: always()
with:
path: Tests/*.xml |
I gett |
make sure you put in @accesscode at the end, otherwise you are still using master |
I retry but still get the same error
|
Seems the check is still in the Line 9606 in e6f45cf
|
Hi @paulpach Rebuild with the latest changes and no longer get token errors
But I don't see any annotations for the failed test in the Actions summary or elsewhere. |
yeah, this is not working yet. they are doing something strange that I have not managed to reproduce |
Hi,
I'm trying to setup nunit-reporter with my .NET 6 project
I have
But the reporter step fails with
Can you tell me what is wrong with my setup?
Cheers,
Jose
The text was updated successfully, but these errors were encountered: