home.social

#conventionalcommit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #conventionalcommit, aggregated by home.social.

  1. Xanatos :godot: @[email protected] ·

    Okay I just get the task of training my colleges to use conventional commits in the future.
    Really happy that we start to use that all my learning wasn't wasted for my daily job.

    So let's get your commit messages sorted out, yeah.

    #GIt #ConventionalCommit #Developer #Programming #VCS

    #git #conventionalcommit #developer #programming #vcs
  2. Xanatos :godot: @[email protected] ·

    Okay I just get the task of training my colleges to use conventional commits in the future.
    Really happy that we start to use that all my learning wasn't wasted for my daily job.

    So let's get your commit messages sorted out, yeah.

    #GIt #ConventionalCommit #Developer #Programming #VCS

    #git #conventionalcommit #developer #programming #vcs
  3. Xanatos :godot: @[email protected] ·

    Okay I just get the task of training my colleges to use conventional commits in the future.
    Really happy that we start to use that all my learning wasn't wasted for my daily job.

    So let's get your commit messages sorted out, yeah.

    #GIt #ConventionalCommit #Developer #Programming #VCS

    #git #conventionalcommit #developer #programming #vcs
  4. Xanatos :godot: @[email protected] ·

    Okay I just get the task of training my colleges to use conventional commits in the future.
    Really happy that we start to use that all my learning wasn't wasted for my daily job.

    So let's get your commit messages sorted out, yeah.

    #GIt #ConventionalCommit #Developer #Programming #VCS

    #git #conventionalcommit #developer #programming #vcs
  5. slackline :emacs: :orgmode: @[email protected] ·

    @guerda @cark I've been trying to adhere to conventional commits too and find it quite useful.

    I like the convention of including the module/function name in parentheses after the type of commit, e.g. `bug(module1): capture TypeError`

    #git #conventionalcommit

    #git #conventionalcommit
  6. slackline :emacs: :orgmode: @[email protected] ·

    @guerda @cark I've been trying to adhere to conventional commits too and find it quite useful.

    I like the convention of including the module/function name in parentheses after the type of commit, e.g. `bug(module1): capture TypeError`

    #git #conventionalcommit

    #git #conventionalcommit
  7. slackline :emacs: :orgmode: @[email protected] ·

    @guerda @cark I've been trying to adhere to conventional commits too and find it quite useful.

    I like the convention of including the module/function name in parentheses after the type of commit, e.g. `bug(module1): capture TypeError`

    #git #conventionalcommit

    #git #conventionalcommit
  8. slackline :emacs: :orgmode: @[email protected] ·

    @guerda @cark I've been trying to adhere to conventional commits too and find it quite useful.

    I like the convention of including the module/function name in parentheses after the type of commit, e.g. `bug(module1): capture TypeError`

    #git #conventionalcommit

    #conventionalcommit #git
  9. slackline :emacs: :orgmode: @[email protected] ·

    @guerda @cark I've been trying to adhere to conventional commits too and find it quite useful.

    I like the convention of including the module/function name in parentheses after the type of commit, e.g. `bug(module1): capture TypeError`

    #git #conventionalcommit

    #git #conventionalcommit
  10. Michael Hanke @[email protected] ·

    Who can help me reduce my dependency on #github? I am looking for (proven) alternatives to PR-based workflows for collaborative development (beyond patches by email). I am particularly concerned about the separation of essential information from the source #Git repo -- for example in PR descriptions/tags from which versions are determined and changelogs are generated.

    I am already looking at #radicle, and #ConventionalCommit (via something like commitizen-tools.github.io/com).

    TIA!

    #fedihelp #boost

    #boost #fedihelp #conventionalcommit #radicle #git #github
  11. Michael Hanke @[email protected] ·

    Who can help me reduce my dependency on #github? I am looking for (proven) alternatives to PR-based workflows for collaborative development (beyond patches by email). I am particularly concerned about the separation of essential information from the source #Git repo -- for example in PR descriptions/tags from which versions are determined and changelogs are generated.

    I am already looking at #radicle, and #ConventionalCommit (via something like commitizen-tools.github.io/com).

    TIA!

    #fedihelp #boost

    #boost #fedihelp #conventionalcommit #radicle #git #github
  12. Michael Hanke @[email protected] ·

    Who can help me reduce my dependency on #github? I am looking for (proven) alternatives to PR-based workflows for collaborative development (beyond patches by email). I am particularly concerned about the separation of essential information from the source #Git repo -- for example in PR descriptions/tags from which versions are determined and changelogs are generated.

    I am already looking at #radicle, and #ConventionalCommit (via something like commitizen-tools.github.io/com).

    TIA!

    #fedihelp #boost

    #boost #fedihelp #conventionalcommit #radicle #git #github
  13. Michael Hanke @mih ·

    Who can help me reduce my dependency on ? I am looking for (proven) alternatives to PR-based workflows for collaborative development (beyond patches by email). I am particularly concerned about the separation of essential information from the source repo -- for example in PR descriptions/tags from which versions are determined and changelogs are generated.

    I am already looking at , and (via something like commitizen-tools.github.io/com).

    TIA!

    #boost #fedihelp #conventionalcommit #radicle #git #github
  14. Michael Hanke @[email protected] ·

    Who can help me reduce my dependency on #github? I am looking for (proven) alternatives to PR-based workflows for collaborative development (beyond patches by email). I am particularly concerned about the separation of essential information from the source #Git repo -- for example in PR descriptions/tags from which versions are determined and changelogs are generated.

    I am already looking at #radicle, and #ConventionalCommit (via something like commitizen-tools.github.io/com).

    TIA!

    #fedihelp #boost

    #boost #fedihelp #conventionalcommit #radicle #git #github
  15. Benoît B. @[email protected] ·

    @BenjaminFaliere

    Je pratique le #conventionalCommit depuis une belle lurette, et je recommande.

    C'est par ailleurs très pratique pour générer automatiquement des « release notes ».

    #conventionalcommit
  16. Benoît B. @[email protected] ·

    @BenjaminFaliere

    Je pratique le #conventionalCommit depuis une belle lurette, et je recommande.

    C'est par ailleurs très pratique pour générer automatiquement des « release notes ».

    #conventionalcommit
  17. Benoît B. @[email protected] ·

    @BenjaminFaliere

    Je pratique le #conventionalCommit depuis une belle lurette, et je recommande.

    C'est par ailleurs très pratique pour générer automatiquement des « release notes ».

    #conventionalcommit
  18. Mark Derricutt (talios) @[email protected] ·

    Neat -- a new #ConventionalCommit versioning policy plugin for newly release #ApacheMaven maven-release-plugin 3.0.0 that just dropped (note the lack of a -M milestone qualifier!!).

    github.com/nielsbasjes/convent

    This looks kinda cool.

    #conventionalcommit #apachemaven
  19. Mark Derricutt (talios) @[email protected] ·

    Neat -- a new #ConventionalCommit versioning policy plugin for newly release #ApacheMaven maven-release-plugin 3.0.0 that just dropped (note the lack of a -M milestone qualifier!!).

    github.com/nielsbasjes/convent

    This looks kinda cool.

    #conventionalcommit #apachemaven
  20. Mark Derricutt (talios) @[email protected] ·

    Neat -- a new #ConventionalCommit versioning policy plugin for newly release #ApacheMaven maven-release-plugin 3.0.0 that just dropped (note the lack of a -M milestone qualifier!!).

    github.com/nielsbasjes/convent

    This looks kinda cool.

    #conventionalcommit #apachemaven
  21. Mark Derricutt (talios) @[email protected] ·

    Neat -- a new #ConventionalCommit versioning policy plugin for newly release #ApacheMaven maven-release-plugin 3.0.0 that just dropped (note the lack of a -M milestone qualifier!!).

    github.com/nielsbasjes/convent

    This looks kinda cool.

    #apachemaven #conventionalcommit
  22. Mark Derricutt (talios) @[email protected] ·

    Neat -- a new #ConventionalCommit versioning policy plugin for newly release #ApacheMaven maven-release-plugin 3.0.0 that just dropped (note the lack of a -M milestone qualifier!!).

    github.com/nielsbasjes/convent

    This looks kinda cool.

    #conventionalcommit #apachemaven
  23. Alejandro Baez @[email protected] ·

    Started fiddling with #cocogitto. A cli tool to automate #ConventionalCommit stuff. Absolutely a joy to use.

    docs.cocogitto.io/

    #conventionalcommit #cocogitto
  24. Alejandro Baez @zeab ·

    Started fiddling with . A cli tool to automate stuff. Absolutely a joy to use.

    docs.cocogitto.io/

    #cocogitto #conventionalcommit
  25. Alejandro Baez @[email protected] ·

    Started fiddling with #cocogitto. A cli tool to automate #ConventionalCommit stuff. Absolutely a joy to use.

    docs.cocogitto.io/

    #cocogitto #conventionalcommit