Anisse on Nostr: It's 2024 and GitHub still encourages bad development processes: - it has no commit ...
It's 2024 and GitHub still encourages bad development processes:
- it has no commit message review UI (like Gerrit or ... e-mail 😬). Good commit messages are essential to long term projects, and not encouraging reviews if bad.
- GitHub actions don't test each commit independently, meaning you can very easily break bisectability of issues (there are workarounds)
- and it tends to encourage squash and merge (as a result of those two previous points?), which is only good for write-only projects
#Github
Published at
2024-05-22 09:24:16Event JSON
{
"id": "6a90824c86e31385d1b08c52cb069f2af46f78c1db1683efcb36eb168a430a7a",
"pubkey": "51861d8ef6d0b4bb0d6af0da4aad333d2fbad46d503ba124ab035734e7095740",
"created_at": 1716362656,
"kind": 1,
"tags": [
[
"t",
"GitHub"
],
[
"proxy",
"https://social.treehouse.systems/users/Aissen/statuses/112483543056496062",
"activitypub"
]
],
"content": "It's 2024 and GitHub still encourages bad development processes:\n - it has no commit message review UI (like Gerrit or ... e-mail 😬). Good commit messages are essential to long term projects, and not encouraging reviews if bad.\n - GitHub actions don't test each commit independently, meaning you can very easily break bisectability of issues (there are workarounds)\n - and it tends to encourage squash and merge (as a result of those two previous points?), which is only good for write-only projects \n\n#Github",
"sig": "b8afb967fc0dbe2ec5ee65e2b2350e228b1ae9dd42a3df1aabb24e2de209f26608916ee2909fa942ee5d6b9c4fd28bda1ed7ffd3bdeb4b61e35b77876cdb6a32"
}