-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
Fix ci hanging on md file changes #428
Comments
We have configured AppVeyor to skip commits that only change markdown files, because building those isn't really necessary... Is this an issue? |
Yeah I think it is still an issue, will test later |
I knew what you meant, you didn't need to test it... This is more or less expected behavior, AppVeyor never starts a build for these commits, and Github waits for a build success notification that never comes. If you feel this is a big annoyance, we can remove the lines I mentioned earlier from |
If we remove that line, AppVeyor will build for md changes and return a status? |
Let's do that |
Is it possible to simply return success when only md is changed is appveyor? |
Seems like there is no standard way to do that, no.
In my opinion this is a minor annoyance that happens rarely enough that it can be overlooked... it only affects PRs whose last commit changes markdown files only. By removing the skip of such commits, we will be stressing a free service unnecessarily on every commit that simply changes the Readme, etc. I think it's a small price to pay... |
yeah that's fine |
We can do something like this. |
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Old issue with many CI updates since. If still a problem reopen. |
AppVeyor ci build hangs when only changes are MD files
The text was updated successfully, but these errors were encountered: