Rasul Time

TLDR: Just put the fucking Issue ID in the commit message, you asshat! I keep reading about Conventional Commits , and I think they are somewhat contrived and over complicate a simple requirement of commits: What context was a change made for. As we all know, information is somewhat useless without context. And I feel the same what about commit messages. And the best context in a commit message a link to the original Ticket in the Issue Tracking system. Most Issue Tracking systems support linking to the SCM , so that you can have a bi-directional link. If you look at an issue you can have a list of SCM changes done for that issue. For example, here is a JIRA issue showing what code change was done for it: And if I look into my SCM I can see the JIRA issues that were used to make changes: And the way to do this is to always have the Issue ID in the commit message. That's it. JIRA has this feature, so does Git Hub. That's all you need to do. Every commit message ...

I am currently learning Apache Tinkerpop . An excellent resource is the free online book PRACTICAL GREMLIN by Kelvin R. Lawrence . And one part of this following this book requires one to setup a Gremlin console. And this was a pain to do each time I would start reading/following the book. So I created a Docker Image which contains the Gremlin Console with the air-routes data preloaded so that you can start working immediately. Pull and Run Image docker pull srasul/gremlin-console-air-routes-data:latest docker run -it srasul/gremlin-console-air-routes-data:latest Example $ docker run -it srasul/gremlin-console-air-routes-data:latest Apr 12, 2020 10:24:01 PM java.util.prefs.FileSystemPreferences$1 run INFO: Created user preferences directory. \,,,/ (o o) -----oOOo-(3)-oOOo----- plugin activated: tinkerpop.server plugin activated: tinkerpop.utilities plugin activated: tinkerpop.tinkergraph gremlin> g ==>graphtraversalsource[tinkergraph[vertices:3742 e...