Skip to content

Commit

Permalink
Create code-of-repo-conduct.md
Browse files Browse the repository at this point in the history
  • Loading branch information
refaktor authored Mar 24, 2024
1 parent f5c559b commit b783c1f
Showing 1 changed file with 20 additions and 0 deletions.
20 changes: 20 additions & 0 deletions code-of-repo-conduct.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Code of repository conduct

With recent HN post a lot of new people came to follow development of Rye. We probably all want Rye updates and general state of Rye repository to
be "a good product" to follow too.

Here we try to come up with some directives, we could follow to achieve this. Everybody is are welcome to propose changes.

We shouldn't have too many principles (or rules), we are not trying to create a bureaucracy here. Just the really necessary ones, the rest is advice or knowledge base ...

## Principles we really try to follow

1. Main branch shouldn't be left in a failed state (the red cross)
2. PRs that are meant for merging should also pass all checks
3. Each new builtin should have a docstring written and at least few tests

## Q&A

How can I create commits / PR-s / merge them so that Github homepage feed is as informative as possible?

...

0 comments on commit b783c1f

Please sign in to comment.