Update WORKSPACE

[kpol-lgx]

Delete one of the two identical lines.

What this PR does / why we need it:
At the beginning of WORKSPACE, the parameters of the two load functions are exactly the same. So maybe one of them should be removed.

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive", "http_file")
load(
    "@bazel_tools//tools/build_defs/repo:http.bzl",
    "http_archive",
    "http_file",
)

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

NONE

[kubevirt-bot]

Hi @kpol-lgx. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[awels]

/lgtm
/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [awels]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[akalenyu]

/hold
weird, 5 commits?

[awels]

It will get squashed into a single commit before merging.

[akalenyu]

It will get squashed into a single commit before merging.

Hmm look at the diff, it looks like unrelated changes and commits got pulled into this PR

[awels]

I see the WORKSPACE and the documentation changes. Are you seeing something else?

[akalenyu]

I see the WORKSPACE and the documentation changes. Are you seeing something else?

[awels]

So you want just the WORKSPACE and not the documentation change?

[akalenyu]

So you want just the WORKSPACE and not the documentation change?

Yes, I doubt the author wants to pull someone elses commit as well

[kubevirt-bot]

@kpol-lgx: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cdi-apidocs	12bfb04	link	false	/test pull-cdi-apidocs
pull-containerized-data-importer-e2e-hpp-previous	12bfb04	link	true	/test pull-containerized-data-importer-e2e-hpp-previous
pull-containerized-data-importer-e2e-ceph-wffc	12bfb04	link	true	/test pull-containerized-data-importer-e2e-ceph-wffc

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. I understand the commands that are listed here.

[kubevirt-bot]

PR needs rebase.

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.

[kubevirt-bot]

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

[kubevirt-bot]

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