Skip to content

Commit 9aa2ec4

Browse files
committed
fix reset and document it
1 parent f1a67d3 commit 9aa2ec4

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
lines changed

docs/dev/release.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -286,6 +286,28 @@ You can see an [example fixed PR here for certified version 1.9.1](https://githu
286286
287287
After the PR is approved it will soon appear in the [Atlas Operator openshift cluster](https://console-openshift-console.apps.atlas.operator.mongokubernetes.com)
288288
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+
289311
# Post install hook release
290312

291313
If changes have been made to the post install hook (mongodb-atlas-kubernetes/cmd/post-install/main.go).

scripts/reset-rh.sh

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@
1313
# See the License for the specific language governing permissions and
1414
# limitations under the License.
1515

16+
set -euo pipefail
17+
1618
# Check if an argument is provided
1719
if [ -z "$1" ]; then
1820
echo "Error: No target specified."

0 commit comments

Comments
 (0)