{"thread":{"id":"56349","subject":"Feature Idea: Expanding git to support automatic Semver stamping","startedAt":"2021-08-22T19:29:31Z","lastAt":"2021-08-23T06:45:18Z","messageCount":2,"participants":["Pavel Rogovoy","Bagas Sanjaya"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"433332","messageId":"CA+NVOTBjgQ60hUZyRcK=igEP5=PSJqUFKf4Z-wYr=7+ESp3Ziw@mail.gmail.com","threadId":"56349","inReplyTo":null,"subject":"Feature Idea: Expanding git to support automatic Semver stamping","fromName":"Pavel Rogovoy","fromEmail":"p.rogovoy@gmail.com","sentAt":"2021-08-22T19:28:53Z","receivedAt":"2021-08-22T19:29:31Z","isPatch":false,"sender":{"key":"p.rogovoy@gmail.com","avatar":null},"body":"Hi all,\n\nMy name is Pavel Rogovoy and I am a git enthusiast. I have developed a\ngit-based generic version stamping system that is compliant with the\nSemver standard and I believe it can be integrated into git as a\nsub-command such as git stamp in the form of an external plugin or a\ncomplete rewrite into git’s source code.\n\nI welcome you to take a look at the stamping utility:\nhttps://github.com/final-israel/vmn\n\nI will be happy to discuss the main benefits of such a move with you.\nHere are just some:\n\n- Effortless version management and state recovery for single or\nmultiple  repositories.\n- Can be used as a convenient git submodule alternative.\n- Way for storing metadata about a version such as: release notes and\nbuild metadata.\n\nPlease let me know if such a feature is of interest to be integrated\ninto git. I personally am willing to contribute and maintain this\nfeature in case you will find it useful for expanding git’s\ncapabilities.\n\nBest,\nPavel Rogovoy\n"},{"id":"433344","messageId":"e478d313-e773-6d83-7d7e-ffce2a4fa0b9@gmail.com","threadId":"56349","inReplyTo":"CA+NVOTBjgQ60hUZyRcK=igEP5=PSJqUFKf4Z-wYr=7+ESp3Ziw@mail.gmail.com","subject":"Re: Feature Idea: Expanding git to support automatic Semver stamping","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2021-08-23T06:45:12Z","receivedAt":"2021-08-23T06:45:18Z","isPatch":false,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"On 23/08/21 02.28, Pavel Rogovoy wrote:\n> Hi all,\n> \n> My name is Pavel Rogovoy and I am a git enthusiast. I have developed a\n> git-based generic version stamping system that is compliant with the\n> Semver standard and I believe it can be integrated into git as a\n> sub-command such as git stamp in the form of an external plugin or a\n> complete rewrite into git’s source code.\n> \n\nI like the idea of automatic semver tagging, especially on case when \ndevelopers do releases quickly (with manual tagging, they must know last \ntag version in order for the new tag version to be correctly greater \nthan previous).\n\n> I welcome you to take a look at the stamping utility:\n> https://github.com/final-israel/vmn\n> \n> I will be happy to discuss the main benefits of such a move with you.\n> Here are just some:\n> \n> - Effortless version management and state recovery for single or\n> multiple  repositories.\n\nIf you `git checkout <something>`, you get whatever your code in \n<something>'s commit; no need for external tools.\n\n> - Can be used as a convenient git submodule alternative.\nI saw \"root app\" concept [1] in vmn, which is roughly superproject in \ngit-submodule. But looking at resulting `vmn show`, it more like \nmetadata for CI job.\n\nWhen developers clone vmn-ed root app repo, they only get code for root \napp only, whereas when they clone normal git repo with submodule, they \ncan initialize any submodules used and have all history of them on their \nfingers.\n\n[1]: https://github.com/final-israel/vmn#root-apps\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"}]}