You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,18 +39,18 @@ We strive to maintain a consistent coding style throughout the project. Please f
39
39
40
40
## Submitting a pull request
41
41
When you have made changes to the codebase that you would like to contribute back, please follow these steps:
42
-
1. Fork the repository and create a new branch from `main`.
42
+
1. Fork the repository and create a new branch from `develop`.
43
43
2. Make your changes and ensure that the code passes all tests.
44
44
3. Write tests for your changes, if applicable.
45
45
4. Update the documentation to reflect your changes, if applicable.
46
-
5. Submit a pull request to the `main` branch.
46
+
5. Submit a pull request to the `develop` branch.
47
47
We will review your pull request as soon as possible. Please be patient and open to feedback. We appreciate your contributions!
48
48
49
49
## Release Process
50
50
**NOTE: The default branch `@develop` is not guaranteed to be stable and you should always use published release versions in your testing and production.**
51
51
52
52
- All pull requests are merged to the default develop branch after initial unit tests and integration tests are passing and required code review requirements are met.
53
-
- We checkout a pre-release branch to prepare for an upcoming release.
53
+
- We checkout a pre-release branch to prepare for an upcoming release with the pattern `prerelease-0.1.xx`.
54
54
- We perform additional manual and automated tests in this branch to make sure there are no regressions.
55
55
- Once we are ready we tag the head of our release branch and perform a release on it.
56
56
- Tagged releases are published as actions and they are the most suitable to be used in production.
0 commit comments