Skip to content

docs: fix stale contribution and e2e debug instructions #9154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
immanuwell wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: fix stale contribution and e2e debug instructions #9154

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -231,7 +231,7 @@ To run a single rekt test using the `e2e-debug.sh` script, follow these instruct
./hack/e2e-debug.sh TestPingSourceWithSinkRef ./test/rekt
```

This will run the specified rekt test (`TestMyRektScenario` in this case) from the provided directory (`test/rekt/scenarios`).
This will run the specified rekt test (`TestPingSourceWithSinkRef` in this case) from the provided directory (`./test/rekt`).

**Note:** Ensure that you have the necessary dependencies and configurations set up before running the test.

Expand Down
10 changes: 5 additions & 5 deletions hack/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ creating releases.

1. Click the Branch dropdown.
1. Type the desired `release-X.Y` branch name into the search box.
1. Click the `Create branch: release-X.Y from 'master'` button. _You must have
1. Click the `Create branch: release-X.Y from 'main'` button. _You must have
write permissions to the repo to create a branch._

Prow will detect the new release branch and run the `release.sh` script. If
Expand All @@ -43,10 +43,10 @@ creating releases.
git fetch upstream
```

1. Create a `release-X.Y` branch from `upstream/master`.
1. Create a `release-X.Y` branch from `upstream/main`.

```sh
git branch --no-track release-X.Y upstream/master
git branch --no-track release-X.Y upstream/main
```

1. Push the branch to upstream.
Expand Down Expand Up @@ -80,10 +80,10 @@ The major version release job is currently called
1. Create a branch based on the desired `release-X.Y` branch.

```sh
git co -b my-backport-branch upstream/release-X.Y
git checkout -b my-backport-branch upstream/release-X.Y
```

1. Cherry-pick desired commits from master into the new branch.
1. Cherry-pick desired commits from main into the new branch.

```sh
git cherry-pick <commitid>
Expand Down
Loading