Can we support the feature not to build if .drone.yml not detected?
Since I got some users are using the very old code base, the build will be meaningless but only the wasting of resource.
Thanks.
As Drone is very new and young, I believe that I’m not the only one migrate the CI platform to Drone, the problem here is, some of the project contributors send pull request based on a commit before switching to Drone, so as I said build will be meaningless but only the wasting of resource.
Drone does fail with an error if the yaml file doesn’t exist.
It is likely that GitHub is returning the yaml using the merge commit. This means that even if the yaml did not exist in the fork / base, it does exist in the target branch and is therefore returned by the API.
It is likely that GitHub is returning the yaml using the merge commit. This means that even if the yaml did not exist in the fork / base, it does exist in the target branch and is therefore returned by the API.
So this looks like isn’t a correct behavior? I’m not sure if I understand correctly, but even there isn’t drone.yml, it’ll still use the git plugin to clone my repository which I think it’s not correct.
Hi @bradrydzewski, so is there any chance to do something for this issue?
This is the problem I mention that happened:
This PR was too old and contained no .drone.yml until I rebased and added it:
Thanks!