• 94 Posts
  • 181 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle



































  • cacheson@kbin.socialOPtoanime_irl@kbin.socialanime_irl
    link
    fedilink
    arrow-up
    2
    ·
    8 months ago

    I’ve been trying to post this for a month, and kept getting the “we are working on resolving issues” error. I thought that there was some bug making me unable to post here anymore. Just noticed that the PNG version that I was trying to upload was 7.8mb, so I guess kbin must have been choking on that.


  • From the PR comments:

    Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, © engaging with the Contributor on improving their patch quality.

    I asked around and asked in the C4 specification matrix room.
    And the reason is actually simple. If you merge bad code, have a record of proof in git (pull requests aren’t forever it’s only a github/gitlab thing).

    So the idea is if you merge bad code you have proof in the git record that there is a bad actor. You can always revert the commit again or fix it. And the record can act as a proof in case the community want to get rid of bad actors.