You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build status badge on the README.md is referring to the "ghuntley/reactiveui" project in AppVeyor, which is reporting the build status as "unknown".
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Presumably the build status badge should be referring to the "dotnetfoundation/reactiveui" project, which is running for PRs.
What is the motivation / use case for changing the behavior?
Radiating the status of the build is a good indicator of the status of the project to potential new contributors (and good motivation to keep the build green 😀)
Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and development snapshot
N/A
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I would submit the PR to fix it myself, but AppVeyor appears to want the internal project ID in the build status link, and I was not able to find that ID with a quick search. Someone with direct access to the AppVeyor build could probably find it faster.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
README bug
What is the current behavior?
The build status badge on the README.md is referring to the "ghuntley/reactiveui" project in AppVeyor, which is reporting the build status as "unknown".
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
See the repo home page
What is the expected behavior?
Presumably the build status badge should be referring to the "dotnetfoundation/reactiveui" project, which is running for PRs.
What is the motivation / use case for changing the behavior?
Radiating the status of the build is a good indicator of the status of the project to potential new contributors (and good motivation to keep the build green 😀)
Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and development snapshot
N/A
Other information (e.g. stacktraces, related issues, suggestions how to fix)
I would submit the PR to fix it myself, but AppVeyor appears to want the internal project ID in the build status link, and I was not able to find that ID with a quick search. Someone with direct access to the AppVeyor build could probably find it faster.
The text was updated successfully, but these errors were encountered: