A modern programming language that makes developers happier.

kotlinlang

Currently, we agreed on the following development workflow:
1. New major changes go to a separate branch.
2. A PR should be opened as draft until it's ready for review.
3. When it's ready, remove the draft status and assign a reviewer.
4. When an agreement is achieved, the PR's author merges the PR. GH's "rebase and merge" button is preferred, but in some special cases it's OK to use "create a merge commit" option.


It seems I can't edit the message above, maybe because it's too old. Let's give updates here.

Update to the 4th step: anyone can merge the PR, not only the author (<https://github.com/krzema12/kotlin-python/pull/34#issuecomment-920804409>).