kubevirt
refactor : fix typo and modify code to make it more readable
Is your feature request related to a problem? Please describe:
-
While analyzing the code, there are typos in the code and comments, so I'm trying to fix them. (One question is, is the word "behaviour" a typo for "behavior"?)
-
modify code to make it more readable
Describe the solution you'd like: A clear and concise description of what you want to happen.
Describe alternatives you've considered: A clear and concise description of any alternative solutions or features you've considered.
Additional context: Add any other context or screenshots about the feature request here.
@yj-yoo: Can not set label good-first-issue: Must be member in one of these teams: [kubevirtkubevirt-label]
In response to this:
/label good-first-issue
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.
Welcome @yj-yoo and thanks for opening this issue! In answer to one of your questions: 'behaviour' is the British English spelling of 'behavior', which is American English. (This is relatively common with -our suffix words in British English; another common one is -ise/-ize, eg 'realise' in British English is 'realize' in American English.)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
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-sigs/prow repository.