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
We open feature branches from `develop` and merge them back via pull requests. The `main` branch holds the current production release.
213
+
214
+
There are 3 remote environments where the code is deployed:
215
+
216
+
1.`production` - the production environment that is automatically deployed from the `main` branch
217
+
2.`staging` - the staging environment that is automatically deployed from the `develop` branch and is used to test and review the code before it is deployed to production
218
+
3.`testing` - this environment is used to deploy feature branches people are working on and need to test in a real environment
219
+
220
+
## Using the testing environment
221
+
222
+
In order to deploy a branch to testing, do this:
223
+
224
+
1. talk to the team to make sure nobody is actively using the testing environment at the moment
225
+
2. push the branch to the remote repository
226
+
3. open the [deploy action](https://github.com/dm3-org/dm3/actions/workflows/deploy.yml)
227
+
4. click on `Run workflow` (right side of the screen) 
228
+
5. select the branch you want to deploy
229
+
6. click on the green `Run workflow` button
230
+
231
+
Please note: if you select the `main` or `develop` branches, they will be deployed to `production` and `staging` respectively. All other branches will be deployed to `testing`.
232
+
233
+
## Pull Requests
234
+
235
+
In order to merge a feature branch into `develop`, you need to open a pull request. The pull request will be reviewed by the team and merged if it is approved. The pull request should have a meaningful title and description, and should be linked to the issue it is solving. Please also make sure that the code is properly tested and that the tests are passing. If you need help with testing, please ask the team. Ideally, link the pull request to the issue it is solving.
236
+
237
+
Once you created a pull request, letting the team know about it is a good idea. Reach out to do so.
0 commit comments