Hi Jody,
For what it is worth, I do this on projects like GeoMesa with merge
squashes both as I put a PR and when I merge a PR. This means that the
first line of commit will have the ticket number from the first commit.
Generally, I like linear histories with one commits solving one ticket!
Okay, I will do my best to adjust my workflow; and use git interactive
rebase when I fail :)
Any other feedback on the geotools templates?
--
Jody Garnett
On Thu, 9 Jan 2020 at 09:50, Nuno Oliveira
wrote:
> I cannot stress enough how valuable this is:
>
> When you have to clean up problems in
I cannot stress enough how valuable this is:
> When you have to clean up problems in code, being able to annotate the
> code (git blame), find the origin,
> track the original description and
> discussion, and the people involved in it, is invaluable
The other day I had to investigate what look li
