latest 20 messages by bmbouter
+
[2017-06-18T15:33:11Z]
bmbouter
kleinweby++
+
[2017-06-18T15:33:08Z]
bmbouter
thank you
+
[2017-06-18T15:33:06Z]
bmbouter
bookmarks it
+
[2017-06-18T15:33:04Z]
bmbouter
kleinweby: that is it!
+
[2017-06-18T15:10:37Z]
bmbouter
can't find the url now
+
[2017-06-18T15:10:32Z]
bmbouter
I know this is possible but I remember the url was not intuative
+
[2017-06-18T15:10:24Z]
bmbouter
specifically for https://github.com/pulp/
+
[2017-06-18T15:10:15Z]
bmbouter
how can I list all of the pull requests for all repos in an organization?
+
[2017-03-17T16:30:51Z]
bmbouter
the config I have doesn't let me choose
+
[2017-03-17T16:30:45Z]
bmbouter
kbs: yeah those are for webhooks. this is in the tab below webhooks so it's a 'service'
+
[2017-03-17T15:57:56Z]
bmbouter
np. I want to learn more I don't need an official response from an employee
+
[2017-03-17T15:55:31Z]
bmbouter
so for github's purposes when are those services expected to be notified? Upon merge or when a pr is opened, or.. ?
+
[2017-03-17T15:55:00Z]
bmbouter
so the automation is kicked off by a github configured 'service' called planio
+
[2017-03-17T15:54:01Z]
bmbouter
kbs: a force push to the forked branch changed the ref number
+
[2017-03-17T15:23:59Z]
bmbouter
kbs, selckin: ty
+
[2017-03-17T15:23:49Z]
bmbouter
I think this explains github's role in it
+
[2017-03-17T15:23:37Z]
bmbouter
agreed
+
[2017-03-17T15:22:06Z]
bmbouter
so maybe the automation is confused because the PR is also from a branch named master?
+
[2017-03-17T15:21:16Z]
bmbouter
yes that makes sense
+
[2017-03-17T15:19:42Z]
bmbouter
this commit was supposed to land (after review) on master