-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppVeyor builds are not shown as PRs checks. #139
Comments
Can the someone with permissions to modify https://ci.appveyor.com/project/fsgit/fsharpx-collections settings try to help or advise? @fsgit @fsprojectsgit ? |
please check #92 |
@sergey-tihon Thanks for help. It seems to work now! What was the solution? |
I am not sure... I created new AppVeyor project and it probably reregistered webhooks in the repo. I personally prefer Azure Pipelines these days (one service, one config file - runs on win, linux and macOS in the same time) |
Description
AppVeyor builds are not triggered for Pull Requests.The builds take place, but the status is not reported on the PR or commits. This may be similar to https://help.appveyor.com/discussions/problems/17150-github-doesnt-report-build-status-on-prsRepro steps
Please provide the steps required to reproduce the problem
Expected behavior
Checks from both Travis and AppVeyor visible.
Actual behavior
Check only from Travis visible.
Known workarounds
Setup your own AppVeyor account, execute the merge on your fork, trigger AppVeyor build and check the results.Check the build status on AppVeyor page manually.Related information
The text was updated successfully, but these errors were encountered: