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

Remove unused fields from GitSource #683

Merged
merged 2 commits into from
Mar 22, 2021

Conversation

imjasonh
Copy link
Contributor

Fixes #682

Changes

Remove HTTPProxy, HTTPSProxy, NoProxy and Flavor. No other code referenced them, so if users set these fields they wouldn't have any effect.

/kind cleanup
/kind api-change

Submitter Checklist

  • [n] Includes tests if functionality changed/was added
  • [n] Includes docs if changes are user-facing
  • [y] Set a kind label on this PR
  • [y] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Remove unused fields from GitSource

/assign @sbose78

@openshift-ci-robot openshift-ci-robot added release-note Label for when a PR has specified a release note kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API labels Mar 18, 2021
@zhangtbj
Copy link
Contributor

Yes, It is initialized by @sbose78 at the beginning.

But no implementation yet. If we don't have a plan to achieve it in the latest release or in 1.0.0, I also suggest remove it first.

Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting. Never saw them before.

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2021
@qu1queee
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 19, 2021
@qu1queee qu1queee removed the lgtm Indicates that a PR is ready to be merged. label Mar 19, 2021
@qu1queee
Copy link
Contributor

qu1queee commented Mar 19, 2021

oh damn, sorry I added/remove my looksgoodtome, it seems we want @sbose78 approval as he originally added this?

@SaschaSchwarze0
Copy link
Member

oh damn, sorry I added/remove my looksgoodtome, it seems we want @sbose78 approval as he originally added this?

Is an API change. I think we then look for lgtm and approve to come from different companies. Although this one is not really an API change. It only removes what was never read by any controller anyway.

@gabemontero
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 22, 2021
Copy link
Member

@sbose78 sbose78 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was an ambitious addition, let's remove it now. We'll probably not use the API when we actually implement this.

@openshift-merge-robot openshift-merge-robot merged commit c086190 into shipwright-io:master Mar 22, 2021
@adambkaplan adambkaplan mentioned this pull request Mar 22, 2021
4 tasks
@qu1queee qu1queee added this to the release-v0.4.0 milestone Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Simplify GitSource proxy settings
8 participants