Skip to content

Commit 1aa4a9d

Browse files
committed
prow steps cleanup
1 parent 79fad13 commit 1aa4a9d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

scripts/prow/README.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,13 @@
33
Use the `add-new-prow-config.sh` script to populate the `$HOME/release/ci-operator/config/openshift/openshift-docs` directory with a new Prow job branch configuration.
44
The script uses the `./openshift-openshift-docs-BRANCH.yaml` template file to create the new job config.
55
After you create the job config, you run the CI make jobs to create the Prow jobs.
6-
Then, open a pull request against the link:git@github.com:openshift/release.git[openshift/release] repository to make the Prow job live for that branch.
6+
Then, open a pull request against the https://github.com/openshift/release repository to make the Prow job live for that branch.
77

88
To add a new job to Prow CI, do the following:
99

1010
. Install link:https://podman.io/docs/installation[podman].
1111

12-
. Fork and clone the link:git@github.com:openshift/release.git[openshift/release] repository to `$HOME/release`.
12+
. Fork and clone the https://github.com/openshift/release repository to `$HOME/release`.
1313

1414
. Create the new branch config by running the `add-new-prow-config.sh` script passing the `$VERSION`, `$BRANCH` and `$DISTROS` variables.
1515
Open a shell prompt in the `openshift-docs/` directory, and run the script passing in the required variables, for example:

0 commit comments

Comments
 (0)