{"thread":{"id":"55031","subject":"Feature Request: View transformation operator for git commit object's read","startedAt":"2021-01-22T17:51:33Z","lastAt":"2021-01-22T17:51:33Z","messageCount":1,"participants":["Jacek Lipiec"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"414978","messageId":"CAPGWkwdGvG5mAg85Ys_0NcwhsRoQ7_ago3nTPVo0oDBBZsf80Q@mail.gmail.com","threadId":"55031","inReplyTo":"001e01d6f0cd$f5aaed30$e100c790$@gmail.com","subject":"Feature Request: View transformation operator for git commit object's read","fromName":"Jacek Lipiec","fromEmail":"jacek.lipiec.bc@gmail.com","sentAt":"2021-01-22T17:27:56Z","receivedAt":"2021-01-22T17:51:33Z","isPatch":false,"sender":{"key":"jacek.lipiec.bc@gmail.com","avatar":null},"body":"Hey,\n\nRecently I was thinking about various methods to bring order to a\nchaos of commit messages that are used throughout the dev space –\nnamely conventional commits and, as alternative, emoji-log. First\nmethod focuses on context, while the second one focuses on\npresentation. Both are trying to bend current GIT capabilities to\nconvey context.\n\nFeature request:\nOption to add a transforming script to the output of all read\noperations on commit object.\n\nExample:\n   $ GIT SHOW FDCCAE00C2D112717306F91A21BFA2BBDDB7DCF6\n   COMMIT FDCCAE00C2D112717306F91A21BFA2BBDDB7DCF6\n   MERGE: 6A235DB 0FCD13B\n   AUTHOR: JACEK LIPIEC <jacek.lipiec.bc@gmail.com>\n   DATE:   THU NOV 7 21:11:45 2020 +0100\n\n       FEAT(LANG): SOME LANG FEATURE\n\nwith view transformation script of, either:\n   /^FEAT\\((?<SCOPE>.+?)\\)/ => 👌\n   /^FEAT\\((?<SCOPE>.+?)\\)/ => <SPAN TITLE=”SCOPE: $SCOPE”>👌</SPAN>\n\nit could work like this:\n   $ GIT CONFIG VIEW.TRANSFORMATION.EMOJI=/^FEAT\\((?<SCOPE>.+?)\\):/ => 👌\n   $ GIT CONFIG VIEW.TRANSFORMATION.FULLTEXT=/^FEAT\\((?<SCOPE>.+?)\\):/\n=> FEATURE $REST WITH SCOPE $SCOPE\n   $ GIT CONFIG\nVIEW.TRANSFORMATION.SHELLSCRIPT=/HOME/JACEK/PARSE-COMMIT-MESSAGE.SH\n   $ GIT SHOW –TRANSFORM=EMOJI FDCCAE00C2D112717306F91A21BFA2BBDDB7DCF6\n   COMMIT FDCCAE00C2D112717306F91A21BFA2BBDDB7DCF6\n   MERGE: 6A235DB 0FCD13B\n   AUTHOR: JACEK LIPIEC <JACEK.LIPIEC.BC@GMAIL.COM>\n   DATE:   THU NOV 7 21:11:45 2020 +0100\n\n      👌: SOME LANG FEATURE\n\n   $ GIT SHOW –TRANSFORM= FULLTEXT FDCCAE00C2D112717306F91A21BFA2BBDDB7DCF6\n   COMMIT FDCCAE00C2D112717306F91A21BFA2BBDDB7DCF6\n   MERGE: 6A235DB 0FCD13B\n   AUTHOR: JACEK LIPIEC <JACEK.LIPIEC.BC@GMAIL.COM>\n   DATE:   THU NOV 7 21:11:45 2020 +0100\n\n    FEATURE SOME LANG FEATURE WITH SCOPE LANG\n\nWould allow both backwards compatibility and an option to return a\nresult in a way that can be easily read by humans, or alternatively,\neasily parsable by machine.\n\nZ poważaniem/Regards,\nJacek Lipiec\n"}]}