Is your feature request related to a problem? Please describe.
Yes, this is related to the practice of everything-as-code; any changes should be made, added, committed to a git repo for tracking purposes.
The git setup should happen as a first step in the instruction and not later on. Doing the following will have the baseline made from the clone then any further changes will be tracked.
Describe the solution you'd like
Move part 4 as part 1 including the tasks linked to cloning the "enablement-ci-cd repository" as it is part of the workspace. This will be then followed by part 2 creating openshift projects which obviously should contain a set of appropriate git commands at the end to push the changes.
Describe alternatives you've considered
Move between 1 and 2, and apply necessary modification to the instructions set.
Is your feature request related to a problem? Please describe. Yes, this is related to the practice of everything-as-code; any changes should be made, added, committed to a git repo for tracking purposes. The git setup should happen as a first step in the instruction and not later on. Doing the following will have the baseline made from the clone then any further changes will be tracked.
Describe the solution you'd like Move part 4 as part 1 including the tasks linked to cloning the "enablement-ci-cd repository" as it is part of the workspace. This will be then followed by part 2 creating openshift projects which obviously should contain a set of appropriate git commands at the end to push the changes.
Describe alternatives you've considered Move between 1 and 2, and apply necessary modification to the instructions set.
Additional context https://openpracticelibrary.com/practice/everything-as-code/