@CaseyBurns I'm trying to setup AppVeyor, but it looks like you beat me to it.
It looks like your AppVeyor project is building branches, but mine is not. I've opened a ticket with AppVeyor to find out why. I suspect there is a problem with the web hooks.
Are you able to bump up my permissions in this repro so I can check the web hooks (I'm not even sure that is an option for collaborators)?
Also, how do you feel about giving me permissions to your AppVeyor project? I think there will be some config changes needed to get the new MVC 6 projects building.
My goal here is to get to one click deployment to NuGet. I have this running for my other projects already. As you can image, I feel uneasy about sharing my NuGet API key. If you like the idea of running the CI from your AppVeyor account (I think it makes sense, but will need a little more initial setup on your part to give me permissions), I think creating a new FluentAssertions.MVC NuGet user with it's own API key, and making it a package owner would be a good solution. I'm happy to sort all the NuGet stuff out.
@CaseyBurns I'm trying to setup AppVeyor, but it looks like you beat me to it.
It looks like your AppVeyor project is building branches, but mine is not. I've opened a ticket with AppVeyor to find out why. I suspect there is a problem with the web hooks.
Are you able to bump up my permissions in this repro so I can check the web hooks (I'm not even sure that is an option for collaborators)?
Also, how do you feel about giving me permissions to your AppVeyor project? I think there will be some config changes needed to get the new MVC 6 projects building.
My goal here is to get to one click deployment to NuGet. I have this running for my other projects already. As you can image, I feel uneasy about sharing my NuGet API key. If you like the idea of running the CI from your AppVeyor account (I think it makes sense, but will need a little more initial setup on your part to give me permissions), I think creating a new
FluentAssertions.MVCNuGet user with it's own API key, and making it a package owner would be a good solution. I'm happy to sort all the NuGet stuff out.Thoughts?