Skip to content

Commit b46d3d4

Browse files
committed
chore: Re-order-content
1 parent f0644c5 commit b46d3d4

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

.github/ISSUE_TEMPLATE/pre-release-getting-started-scripts.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -20,23 +20,8 @@ assignees: ''
2020

2121
Part of <https://github.com/stackabletech/issues/issues/TRACKING_ISSUE>
2222

23-
Replace the items in the task lists below with the applicable Pull Requests (if any).
24-
25-
> [!TIP]
26-
> Create branches with predictable names so the links below work. Remember
27-
> to replace `xx.(x)x` with the appropriate release version:
28-
>
29-
> ```sh
30-
> git stash -m "unsaved work"
31-
> git fetch origin
32-
> git checkout -b fix/getting-started-pre-xx.(x)x origin/main
33-
> ```
34-
>
35-
> Then use the links below to automatically create applicable PRs for each operator
36-
> using the PR template.
37-
3823
In each operator repository, run the following commands. If any updates are
39-
required, open a PR using the links below.
24+
required, open a PR using the applicable link below.
4025

4126
```shell
4227
# Some of the scripts are in a code/ subdirectory
@@ -55,6 +40,21 @@ kind delete cluster && kind create cluster
5540
popd
5641
```
5742

43+
> [!TIP]
44+
> Create branches with predictable names so the links below work. Remember
45+
> to replace `xx.(x)x` with the appropriate release version:
46+
>
47+
> ```sh
48+
> git stash -m "unsaved work"
49+
> git fetch origin
50+
> git checkout -b fix/getting-started-pre-xx.(x)x origin/main
51+
> ```
52+
>
53+
> Then use the links below to automatically create applicable PRs for each operator
54+
> using the PR template.
55+
56+
Replace the items in the task lists below with the applicable Pull Requests (if any).
57+
5858
<!--
5959
The following list was generated by:
6060

0 commit comments

Comments
 (0)