search

kubernetes-csi / csi-release-tools

shared build and test files used by kubernetes-csi projects
Apache License 2.0
21 stars 71 forks source link

go-get-kubernetes.sh is adding replace back to go.mod even with -p #213

Closed sunnylovestiramisu closed 1 year ago

sunnylovestiramisu commented 1 year ago

The generated prs all add the replace back:

https://github.com/kubernetes-csi/csi-driver-host-path/pull/383 https://github.com/kubernetes-csi/external-attacher/pull/395 https://github.com/kubernetes-csi/external-provisioner/pull/834 https://github.com/kubernetes-csi/external-snapshotter/pull/797 https://github.com/kubernetes-csi/lib-volume-populator/pull/61 https://github.com/kubernetes-csi/node-driver-registrar/pull/257 https://github.com/kubernetes-csi/volume-data-source-validator/pull/64 https://github.com/kubernetes-csi/external-health-monitor/pull/149 https://github.com/kubernetes-csi/external-resizer/pull/247 https://github.com/kubernetes-csi/livenessprobe/pull/172 https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/pull/133

/kind bug

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-csi/csi-release-tools/issues/213#issuecomment-1546276239): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.