12:21 <mato> kensan: hannes: Ah, actually there is a good reason for opening a new PR vs. editing an existing one, which is that if you edit existing $THING, Github does not send an email notification.

12:22 <mato> Hence I didn't know you'd changed anything in #178 until I looked at the surf-build logs 5mins ago. (Which is failing since the build.sh script landed after the base you're using for the PR)

12:23 <hannes> mato: you should be notified by force-pushes, although not by edits, that is true

12:28 <kensan> mato: I see, what is your preferred way of doing things?

12:28 <kensan> mato: I updated the pull request via force-push and edited the PR title and text yesterday evening.

12:29 <kensan> mato: I can rebase it on master and update the PR again.

12:29 <mato> Weird, I got no notifications at all. Not in the Docker Slack thingy that monitors Solo5 PRs either. Must be a Github bug.

12:29 <mato> kensan: I don't care either way, just pointing out that I didn't get the notifications...

12:30 <mato> kensan: If you can rebase against master and force-push again, that'd be good, at least I'll see if surf-build picks it up correctly.

12:31 <mato> The last notification I got was "will update the PR once I have something". Odd.

12:34 <kensan> mato: done

12:35 <mato> kensan: Thanks. The CI has picked it up. Still no notifications (email or Slack).

13:16 <kensan> mato: Hm, do not know why you get no notifications. Imho github should send you a mail.

21:48 <hannes> lobo: btw, its back now :)