Event JSON
{
"id": "dbe369aca7098136460aa8f8d133119c99bd936018f7cfe4c1acd3d2514ae75e",
"pubkey": "71aa50fe1290017cbd9493f5a568c4fcf9d1e59e53f03803197d035cb91ce980",
"created_at": 1741070657,
"kind": 1,
"tags": [
[
"t",
"codeberg"
],
[
"t",
"softwaredevelopment"
],
[
"t",
"git"
],
[
"t",
"programming"
],
[
"proxy",
"https://fosstodon.org/@e11bits/114102806600420238",
"web"
],
[
"t",
"github"
],
[
"t",
"gitlab"
],
[
"proxy",
"https://fosstodon.org/users/e11bits/statuses/114102806600420238",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://fosstodon.org/users/e11bits/statuses/114102806600420238",
"pink.momostr"
],
[
"-"
]
],
"content": "I recently had a discussion with a coworker about commit messages. And I wonder what guidelines developers prefer.\n\nPast tense example (Django):\nhttps://docs.djangoproject.com/en/5.1/internals/contributing/committing-code/#committing-guidelines\n\nImperative example:\nhttps://github.com/RomuloOliveira/commit-messages-guide/blob/master/README.md#good-practices\n\nConventional/Semantic:\nhttps://www.conventionalcommits.org/en/v1.0.0/\nand\nhttps://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716\n\nMaybe other styles?\n\n#programming #git #gitlab #github #codeberg #softwaredevelopment",
"sig": "0470f8eaa30144f817901b9aaa92c5053ae2c084f4869166c4edab3743c2e737df5fca7fd775a47aa8bbae3bbd2944ec99f22e92a57e4fa39eb9f881b8c17bf5"
}