MoM - 6th Gathering - Githubissues

lakruzz / gh-phlow

This repository is a template for our default Github issues developer workflow in Praqma

3 stars 2 forks source link

Closed lakruzz closed 7 years ago

lakruzz commented 7 years ago

Kamstrup, Volvo, MAN D&T

lakruzz commented 7 years ago

A small recap.

What choices have been made implicitly in the tool, what if we have long lived branches.

Support for different branching strategies - especially long-lived feature branches and release branches.

lakruzz commented 7 years ago

When we are at a brink of a release - and need to go on to the next. We need a temporary stabilization branch. as in the git-flow.

lakruzz commented 7 years ago

We explain how resuming work on a branch using workon implicitly makes a pull --rebase

This should be configurable.

lakruzz commented 7 years ago

Talking about declarative pipelines.

lakruzz commented 7 years ago

Windows support is required.

lakruzz commented 7 years ago

Dan is suggesting that workonshould take a parameter too - we seem to agrre that the curretn implementation is better.

lakruzz commented 7 years ago

What happens if you forget to wrapupand do workon+ deliver

lakruzz commented 7 years ago

We're talking about Atlassian integration.

Jira+Bitbucket

Jira+GitHub

Volvo hasn't decided yet if they go with one on the other.

lakruzz commented 7 years ago

Jira is already integration with Bitbucket - so maybe it's really just a Jira integration.

lakruzz commented 7 years ago

How do we handle pull requests? It's required

lakruzz commented 7 years ago

Multiple long-lived/integration branch support is required (Samuel)

lakruzz commented 7 years ago

Task creating form the command line? is it relevant? Needed?

lakruzz commented 7 years ago

The Command line focus is kinda cool, and might help people actually use the command line better.

We're discussing - park/share - it's needed.

JKrag commented 7 years ago