#conventionalcommits — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #conventionalcommits, aggregated by home.social.
-
As a companion project to sprig-commit which I published earlier, tonight I created sprig-lint. Similar to #commitlint, it validates the #conventionalCommits format and general styling, but it is implemented as a single #bash 3.2 script with zero dependencies.
-
As a companion project to sprig-commit which I published earlier, tonight I created sprig-lint. Similar to #commitlint, it validates the #conventionalCommits format and general styling, but it is implemented as a single #bash 3.2 script with zero dependencies.
-
As a companion project to sprig-commit which I published earlier, tonight I created sprig-lint. Similar to #commitlint, it validates the #conventionalCommits format and general styling, but it is implemented as a single #bash 3.2 script with zero dependencies.
-
As a companion project to sprig-commit which I published earlier, tonight I created sprig-lint. Similar to #commitlint, it validates the #conventionalCommits format and general styling, but it is implemented as a single #bash 3.2 script with zero dependencies.
-
As a companion project to sprig-commit which I published earlier, tonight I created sprig-lint. Similar to #commitlint, it validates the #conventionalCommits format and general styling, but it is implemented as a single #bash 3.2 script with zero dependencies.
-
I created this small #git hook script that helps you work with #ConventionalCommits and issue tagging for commit messages (eg. #Jira). Zero dependencies, pure #bash. I hope it can be useful to someone.
-
I created this small #git hook script that helps you work with #ConventionalCommits and issue tagging for commit messages (eg. #Jira). Zero dependencies, pure #bash. I hope it can be useful to someone.
-
I created this small #git hook script that helps you work with #ConventionalCommits and issue tagging for commit messages (eg. #Jira). Zero dependencies, pure #bash. I hope it can be useful to someone.
-
I created this small #git hook script that helps you work with #ConventionalCommits and issue tagging for commit messages (eg. #Jira). Zero dependencies, pure #bash. I hope it can be useful to someone.
-
You don't want contributors? Well, enforce #conventionalcommits - because that's how you ensure you don't get any contributors!
-
You don't want contributors? Well, enforce #conventionalcommits - because that's how you ensure you don't get any contributors!
-
You don't want contributors? Well, enforce #conventionalcommits - because that's how you ensure you don't get any contributors!
-
You don't want contributors? Well, enforce #conventionalcommits - because that's how you ensure you don't get any contributors!
-
You don't want contributors? Well, enforce #conventionalcommits - because that's how you ensure you don't get any contributors!
-
Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
-
Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
-
Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
-
Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
-
Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
-
Tác giả đề xuất hệ thống đặt tên commit Git mới, chi tiết hơn Conventional Commits. Nó phân loại rõ ràng thay đổi "Hướng người dùng" (ví dụ: feat, fix) và "Nội bộ" (ví dụ: refactor, chore). Mục tiêu là giúp commit message rõ ràng và dễ hiểu hơn. Bạn nghĩ sao?
#Git #LậpTrình #Commit #ConventionalCommits #PhátTriểnPhầnMềm
#Git #Programming #CommitNaming #SoftwareDevelopment #DevOpshttps://www.reddit.com/r/programming/comments/1pui0hc/commit_naming_system/
-
Just published a guide on using changelogen + a custom AI slash command to auto-generate and clean up your `CHANGELOG.md` from Conventional Commits. Duplicate issues gone, contributor names fixed, semantic bumps handled.
-
Just published a guide on using changelogen + a custom AI slash command to auto-generate and clean up your `CHANGELOG.md` from Conventional Commits. Duplicate issues gone, contributor names fixed, semantic bumps handled.
-
Just published a guide on using changelogen + a custom AI slash command to auto-generate and clean up your `CHANGELOG.md` from Conventional Commits. Duplicate issues gone, contributor names fixed, semantic bumps handled.
-
Just published a guide on using changelogen + a custom AI slash command to auto-generate and clean up your `CHANGELOG.md` from Conventional Commits. Duplicate issues gone, contributor names fixed, semantic bumps handled.
-
Just published a guide on using changelogen + a custom AI slash command to auto-generate and clean up your `CHANGELOG.md` from Conventional Commits. Duplicate issues gone, contributor names fixed, semantic bumps handled.
-
So... I use #gitmoji for my #ConventionalCommits, and I absolutely love it. I've been using semantic-release-gitmoji [1] in order to build a `CHANGELOG.md` file out of the commit history, but it doesn't seem to be particularly well-maintained. I'm currently bumping up against a security vulnerability that I can't patch (reliably) because of a transient dependency, so I'm hoping somebody out there has an alternative approach. A cursory web search turned up bupkis.
I'm not necessarily married to semantic-release, but I like it quite a bit and would prefer to continue using it if possible. (I've used release-please in the past and thought it was decent, as well, so if there's a solution involving that, maybe I'd be up for it.)
Does anybody else build changelogs from conventional commits using gitmoji? If so, what's your stack?
-
So... I use #gitmoji for my #ConventionalCommits, and I absolutely love it. I've been using semantic-release-gitmoji [1] in order to build a `CHANGELOG.md` file out of the commit history, but it doesn't seem to be particularly well-maintained. I'm currently bumping up against a security vulnerability that I can't patch (reliably) because of a transient dependency, so I'm hoping somebody out there has an alternative approach. A cursory web search turned up bupkis.
I'm not necessarily married to semantic-release, but I like it quite a bit and would prefer to continue using it if possible. (I've used release-please in the past and thought it was decent, as well, so if there's a solution involving that, maybe I'd be up for it.)
Does anybody else build changelogs from conventional commits using gitmoji? If so, what's your stack?
-
So... I use #gitmoji for my #ConventionalCommits, and I absolutely love it. I've been using semantic-release-gitmoji [1] in order to build a `CHANGELOG.md` file out of the commit history, but it doesn't seem to be particularly well-maintained. I'm currently bumping up against a security vulnerability that I can't patch (reliably) because of a transient dependency, so I'm hoping somebody out there has an alternative approach. A cursory web search turned up bupkis.
I'm not necessarily married to semantic-release, but I like it quite a bit and would prefer to continue using it if possible. (I've used release-please in the past and thought it was decent, as well, so if there's a solution involving that, maybe I'd be up for it.)
Does anybody else build changelogs from conventional commits using gitmoji? If so, what's your stack?
-
So... I use #gitmoji for my #ConventionalCommits, and I absolutely love it. I've been using semantic-release-gitmoji [1] in order to build a `CHANGELOG.md` file out of the commit history, but it doesn't seem to be particularly well-maintained. I'm currently bumping up against a security vulnerability that I can't patch (reliably) because of a transient dependency, so I'm hoping somebody out there has an alternative approach. A cursory web search turned up bupkis.
I'm not necessarily married to semantic-release, but I like it quite a bit and would prefer to continue using it if possible. (I've used release-please in the past and thought it was decent, as well, so if there's a solution involving that, maybe I'd be up for it.)
Does anybody else build changelogs from conventional commits using gitmoji? If so, what's your stack?
-
So... I use #gitmoji for my #ConventionalCommits, and I absolutely love it. I've been using semantic-release-gitmoji [1] in order to build a `CHANGELOG.md` file out of the commit history, but it doesn't seem to be particularly well-maintained. I'm currently bumping up against a security vulnerability that I can't patch (reliably) because of a transient dependency, so I'm hoping somebody out there has an alternative approach. A cursory web search turned up bupkis.
I'm not necessarily married to semantic-release, but I like it quite a bit and would prefer to continue using it if possible. (I've used release-please in the past and thought it was decent, as well, so if there's a solution involving that, maybe I'd be up for it.)
Does anybody else build changelogs from conventional commits using gitmoji? If so, what's your stack?
-
Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.
-
Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.
-
Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.
-
Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.
-
Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.
-
I'm not thrilled with #Drupal adopting #ConventionalCommits. For one thing, it doesn't properly spec the grammar of the description part. https://www.conventionalcommits.org/en/v1.0.0/
-
I'm not thrilled with #Drupal adopting #ConventionalCommits. For one thing, it doesn't properly spec the grammar of the description part. https://www.conventionalcommits.org/en/v1.0.0/
-
I'm not thrilled with #Drupal adopting #ConventionalCommits. For one thing, it doesn't properly spec the grammar of the description part. https://www.conventionalcommits.org/en/v1.0.0/
-
I'm not thrilled with #Drupal adopting #ConventionalCommits. For one thing, it doesn't properly spec the grammar of the description part. https://www.conventionalcommits.org/en/v1.0.0/
-
I'm not thrilled with #Drupal adopting #ConventionalCommits. For one thing, it doesn't properly spec the grammar of the description part. https://www.conventionalcommits.org/en/v1.0.0/
-
I run from anything with npm in the docs, so I built my own Conventional Commits linter—convcommitlint— simple, open source, GitHub Action included! All human-made, even the blog post. 😅
🔗 https://github.com/coolapso/convcommitlint/
📝 https://blog.coolapso.sh/en/posts/convcommitlint/ -
Using conventional commits at work and someone puts everything as a ‘chore’, but like, I get it.
-
Using conventional commits at work and someone puts everything as a ‘chore’, but like, I get it.
-
Using conventional commits at work and someone puts everything as a ‘chore’, but like, I get it.
-
Using conventional commits at work and someone puts everything as a ‘chore’, but like, I get it.
-
Using conventional commits at work and someone puts everything as a ‘chore’, but like, I get it.
-
PSA: I just updated https://thi.ng/monopub (a tool for synchronized publishing of packages in a monorepo) to add a new option to truncate generated changelogs with a configurable cut-off date (i.e. to exclude older versions). I've set the default cut off to 1st of January 3 years ago. As a result this saves around 1MB of just changelog files per full #ThingUmbrella release (for 200 packages). Older version history can of course still be obtained via Git...
