Open bhouse opened 10 years ago
cc @zz85
maybe the answer is just to have a successful deploy before checking the Update Pull Request after deployment
box, so freeze that option until that happens?
I like the idea that if a deploy hasn't happened before the integration wouldn't do anything.
We ran into a scenario today where we stood up a fresh Samson instance, created a new project for a github repo, checked
Update Pull Request after deployment
, and ran a successful deploy.Since it was the first successful deploy of the project, it covered the PR's for the life of the github repo, and commented on every PR that was already closed.
Some way to grandfather in old PR's on an initial deploy, or whatever, would be nice to avoid this. Consequently this github user, who shall remain nameless, has earned lots of comment points, if that is a thing.