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: docs/dev/release.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -286,6 +286,28 @@ You can see an [example fixed PR here for certified version 1.9.1](https://githu
286
286
287
287
After the PR is approved it will soon appear in the [Atlas Operator openshift cluster](https://console-openshift-console.apps.atlas.operator.mongokubernetes.com)
288
288
289
+
### Fix a RedHat PR
290
+
291
+
If there is a bug in the Redhat PRs, those are best fixed by closing the wrong PR in review and re-issuing a new one from a freshly made branch.
292
+
293
+
In order to redo a PR:
294
+
295
+
1. Close the broken PR(s) at Github.
296
+
1. Fix the isue in the AKO code and merge it.
297
+
1. Reset the local repo copy to re-issue the release using `./script/reset-rh.sh`
298
+
1. Issue the PR again following the normal instructions above for each PR.
299
+
300
+
The `./script/reset-rh.sh` script usage is:
301
+
302
+
```shell
303
+
$ ./script/reset-rh.sh all # to reset all 3 repos
304
+
```
305
+
Or select one or more of `community`, `openshift` or `certified` separated by commas to reset one or more selectively. For example:
306
+
```shell
307
+
$ ./script/reset-rh.sh community,certified # to reset community and certified repos only
308
+
```
309
+
310
+
289
311
# Post install hook release
290
312
291
313
If changes have been made to the post install hook (mongodb-atlas-kubernetes/cmd/post-install/main.go).
0 commit comments