Skip to content
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.

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

Add the instruction on how to use e2e-debug.sh in the doc #7550

Closed
Leo6Leo opened this issue Jan 8, 2024 · 3 comments · Fixed by #7554
Closed

Add the instruction on how to use e2e-debug.sh in the doc #7550

Leo6Leo opened this issue Jan 8, 2024 · 3 comments · Fixed by #7554
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature-request

Comments

@Leo6Leo
Copy link
Member

Leo6Leo commented Jan 8, 2024

Problem
According to #7426, the new command to run single rekt test in the e2e-debug script has been added but the instruction on how to use it is missing from the DEVELOPMENT.md

Persona:
Contributors

Exit Criteria
A clear instruction is added to the DEVELOPMENT.md on how to run a single rekt test with the new e2e-debug script.

Time Estimate (optional):
How many developer-days do you think this may take to resolve? 1

Additional context (optional)
Add any other context about the feature request here.
#7204 has the instruction on how to use this new command

/good-first-issue
/help

Copy link

knative-prow bot commented Jan 8, 2024

@Leo6Leo:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Problem
According to #7426, the new command to run single rekt test in the e2e-debug script has been added but the instruction on how to use it is missing from the DEVELOPMENT.md

Persona:
Contributors

Exit Criteria
A clear instruction is added to the DEVELOPMENT.md on how to run a single rekt test with the new e2e-debug script.

Time Estimate (optional):
How many developer-days do you think this may take to resolve? 1

Additional context (optional)
Add any other context about the feature request here.
#7204 has the instruction on how to use this new command

/good-first-issue
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow knative-prow bot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 8, 2024
@abhayporwals
Copy link
Contributor

hey @Leo6Leo ! I would like to do this in the given timeline.
Anything else you want to share?

@Leo6Leo
Copy link
Member Author

Leo6Leo commented Jan 9, 2024

/assign @professorabhay
Nope! Leave the comment if you have any questions! Thanks for picking up this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants