Thread

1. swiftcoder · 1790174327 · focus · HN ↗

   I think there is a missing pro here on the wiki side: trivial edits are trivial. Even fixing a typo in the docs directory requires PR + approvals + CI. Effectively limiting your docs contributors to folks who are comfortable with a code editor, and git, is a decision

   1. Kinrany · 1790175391 · focus · HN ↗

      Forcing CI and approvals on changes to docs/ is a decision

      1. swiftcoder · 1790178097 · focus · HN ↗

         Entertainingly, excluding a directory from PR approvals is not an option GitHub provides out of the box

         1. pocksuppet · 1790179018 · focus · HN ↗

            Then don't do approvals. Comment "approved" and if someone merges without someone else commenting "approved" someone gets mad at them.

            1. swiftcoder · 1790180567 · focus · HN ↗

               One can always work around tools limitations. The limitations tell us something about how the creators intended it to be held, however

               1. pocksuppet · 1790277430 · focus · HN ↗

                  You don't have to hold a tool the way its creator intended. Do you call yourself a hacker?

Unofficial Hacker News client; not affiliated with Y Combinator.