Johan Abildskov

This has many different consequences and sets of scenarios. Where can I find the user stories or the spec that we are trying to implement? Which branch you work on...

But if it bases the workbranch on master then your changes Will still "disappear"? Den 24. nov. 2017 3.24 PM skrev "Simon Grønborg" : > It would make sense to...

Should we remove git bash from the compatibility matrix until we support it?

For me this is a fun and cool idea - but perhaps with limited benefit. I think it is overkill and filled with caveats as @adamatan mentions. I'd be happy...

It is a good idea. Although the traceability of cause will be amiss ( unless you tag commits with previous commit shas? confusing! ). Another solution could be to use...

Johan learned today that you can provide a commit range using .. to cherry-pick so we should probably also have this as part of the cherry-pick exercise. It should probably...

Hi @Kardelio, Welcome and I am glad that you want to be involved. Yes the scenario you have there is the basic cherry pick scenario. It would also be nice...

We had it happen at a customer some time ago, so I do not remember precisely how the implementation was instated, but you can assume it was "system wide" configuration....

There is already one :) It might also be useful to just skip client side hooks with flags, on each command :) On Wed, Feb 19, 2020 at 1:48 PM...

I assume this is for the hook kata. It should be explicit about which hook to use. As there are hook samples in any git repository.