| 28 | - Updating README. | 28 | - Updating README. |
| 29 | - Updating GitHub Actions. | 29 | - Updating GitHub Actions. |
| 30 | - Hotfixing a critical bug. | 30 | - Hotfixing a critical bug. |
| 31 | 4. Project maintainers will test and can change your code before merging. | 31 | 4. Project maintainers will test and can change your code before merging. To keep our workflow smooth, please ensure the following: |
| | 32 | - The "Allow edits from maintainers" option is checked. |
| | 33 | - Avoid force-pushing your branch once the PR is out of draft state. |
| 32 | 5. To make sure that your contribution remains testable and reviewable, try not to exceed a soft limit of **200 lines of code** (both additions and deletions) per pull request. If you have more to contribute, split it into multiple pull requests. We can also consider creating a separate feature branch for more substantial changes, but please discuss it with the maintainers first. | 34 | 5. To make sure that your contribution remains testable and reviewable, try not to exceed a soft limit of **200 lines of code** (both additions and deletions) per pull request. If you have more to contribute, split it into multiple pull requests. We can also consider creating a separate feature branch for more substantial changes, but please discuss it with the maintainers first. |
| 33 | 6. Write at least somewhat meaningful PR descriptions and commit messages. There's no "right" way to do it, but the following may help with outlining a general structure: | 35 | 6. Write at least somewhat meaningful PR descriptions and commit messages. There's no "right" way to do it, but the following may help with outlining a general structure: |
| 34 | - What is the reason for a change? | 36 | - What is the reason for a change? |