Srinivas Upadhya
Srinivas Upadhya
added test to reproduce #2089
When i wrote gerrit plugin i assumed one review (change-set) can have only one commit. when you make a new commit on an existing review it becomes a new review....
I added support for [gerrit status notifer](https://github.com/srinivasupadhya/gocd-build-status-notifier/releases).
With the https://github.com/ashwanthkumar/gocd-build-github-pull-requests/pull/14 the plugin now polls & checksout to latest revision of a PR. This might not be a problem anymore.
Should we use `+refs/pull/*/head:refs/remotes/origin/pull-request/*` instead of `+refs/pull/*/merge:refs/gh-merge/remotes/origin/*` then? we can use `refs/remotes/origin/pull-request/` to filter pull requests in that case.
That would mean every commit to master would cause new merge commits on github & hence new builds for each PR? if that is the case it could be very...
@ashwanthkumar - we could potentially use merge commits as opposed to top commit of PR for builds. But there is some flakiness inherent to the approach (as you mentioned above)....
Not sure why this isn't documented. But here is the sample code for it. Note: works only on iOS ``` FlutterWebBrowser.events().listen((event) { if (event is RedirectEvent) { onRedirect(event.url); } if...
https://github.com/victorbonnet/flutter_web_browser/issues/44#issuecomment-1127251195