modify #190
modify #190
Conversation
|
/kickstart-test bridge-2devs |
1 similar comment
|
/kickstart-test bridge-2devs |
|
/kickstart-test --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
6 similar comments
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1234 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1224 --skip-testtypes network bridge-2devs |
1 similar comment
|
/kickstart-test --kstest-pr 1224 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
2 similar comments
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
|
/kickstart-test --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
1 similar comment
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
1 similar comment
|
/kickstart-test --kstest-pr 1231 --skip-testtypes network bridge-2devs |
|
/kickstart-test --skip-testtypes network bridge-2devs |
rvykydal
force-pushed
the
master
branch
2 times, most recently
from
b9bc0d9 to
3847f16
Compare
Thank you for your contribution!
Please check that your PR follows these rules:
Code conventions. tl;dr: Follow PEP8, wrap at 100 chars, and provide docstrings.
Commit message conventions. tl;dr: Heading, empty line, longer explanations, all wrapped manually. If in doubt, write a longer commit message with more details.
Tests pass and cover your changes. You can run tests locally manually, or have them run as part of the PR. A team member will have to enable tests manually after inspecting the PR.
If you don't know how, ask us for help!
Release notes and docs if the PR adds something major or changes existing behavior.
If you don't know how, ask us for help!
RHEL rules: If your PR is for a
rhel-*branch, pay special attention to commit messages. Make sure all commit messages include a line linking the commit to a bug, such asResolves: RHEL-123456. For more information, see the complete rules.If you don't know how, ask us for help!
Don't forget - if you don't know how, ask us for help!
And now that you read this all, you can delete it and type your own description of your changes :-)