Bue Petersen

The meeting agenda we called for: I would like to learn the state together with you of git-phlow to know how maintainable it is and what we should have on...

## Observations ## Example - implementing support for Gitlab * I'll need to implement `plugins/gitlab.go` for web-request (compareable to `plugins/jira.go`, for example assign user og authenticate methods. * Also `gitlabmodel.go`...

Your console log output would be nice, I'm not fully sure how to reproduce. But never the less, I think it makes sense to make this issue about never failing...

No worries, we would have to reproduce in a test anyway... so just if some more information about reproducing would also be fine. And as mentioned, this issues should be...

simple fix - update docs at some point

I agree that this is also the behavior I want in the end. It will also make `git phlow web` take me to the current issues, so I for example...

@martinmosegaard and you realize the taking you back to the integration branch will reset your code changes back to something before your changes? Also that if you have a debugger...

Thanks for all the input - issue is on hold until we have defined how we actually want our phlow to work.

@groenborg you're not going to implement this issue... you added labels It is not in scope.

@groenborg can you follow up on this Wednesday morning? Did anyone respond... please lets summarize up what was answered and if it made sense.