git.lain.church game of nomic
Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.

117_Github-repository.md 1.6KB

před 3 roky
123456789101112131415161718192021222324252627
  1. Each rule shall be represented by a file in either the `immutable_rules/` or
  2. `mutable_rules/` directory of the git repository where the game is being
  3. recorded. No other files in the repository shall be constituted to represent a
  4. rule or have the force of a rule.
  5. The master branch of the repository will serve as a representation of the
  6. current game state. No commits are allowed to be made to the master branch
  7. except through the mechanism of a git.lain.church Pull Request.
  8. Pull Requests must perform exactly one of the following actions:
  9. 1. Add a file to one of the rules directory, when a rule is enacted.
  10. 2. Remove a file from one of the rules directories when a rule is repealed.
  11. 3. Modify an existing rule file, when an amendment is made, or repealed, or when
  12. an amendment to an amendment is made or repealed.
  13. 4. Move a rule from either the immutable_rules directory or the mutable_rules
  14. directory to the other one, when a rule is transmuted.
  15. 5. Create a new player file in the `players/` directory
  16. 6. Perform some administrative task on the repository, at the discretion of the
  17. players. Pull Requests of this type can happen outside of the normal turn
  18. order, must be approved by majority vote of all players, and cannot
  19. materially affect the operation of the rules or the game. An example of this
  20. would be removing or replacing the LICENSE or README files.
  21. The proper way to propose a rule-change is a Pull Request. Players vote on Pull
  22. Requests/proposals by putting either "+1" or "-1" as a comment on the Pull
  23. Request, or by using the proper :thumbsup: or :thumbsdown: emoji on the Pull Request comment.