Marcel Hild

I'm still not so sure on wether a new addon is actually needed. But I only see a way to move this into the original addon, by moving some logic...

maybe not. I'll create a new PR to update your original addon to be working with 3.7 then

The following seems to work for `!assigned`, but not for `assigned`. 🤷 ```diff diff --git a/pkg/hubbub/match.go b/pkg/hubbub/match.go index ca279eb..7a625f5 100644 --- a/pkg/hubbub/match.go +++ b/pkg/hubbub/match.go @@ -95,11 +95,11 @@ func preFetchMatch(i...

If you can give me some directions in #292 I'm happy to continue trying to fix it

with `nbformat` we can extract the cells from a notebook and write new cells: ``` import nbformat # Load the notebook with open('notebook.ipynb', 'r') as f: nb = nbformat.read(f, as_version=4)...

> A "bootstrap" command for the bot causes the repo to be pre-populated with the chosen stack content I suggest making this the first milestone. It's ok to assume the...

> IMO actual merge conflicts just don't happen often enough to worry about. maybe I just get it wrong, but arent [these](https://gist.github.com/durandom/0129886d2283e38303ee) all merges to the master while master was...

yeah, I thought @matthewd meant merges while master is red/broken, because you cant merge a PR if it has conflicts. So this is all about keeping master stable. And by...

> Rearranging the actual test-running process I think the test running and travis setup would remain the same. Just the merging is done by a bot. And I dont know...

@matthewd so the master does not turn red, because some code in the PR breaks it, but changes in dependent external libraries? Just trying to understand this