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

make golint more confident #1745

Merged
merged 1 commit into from
Sep 27, 2018

Conversation

paulfantom
Copy link
Contributor

Propagate #1676.

/assign @enxebre @spangenberg

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 27, 2018
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 27, 2018
@spangenberg
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 27, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: paulfantom, spangenberg

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-merge-robot openshift-merge-robot merged commit 3fc5496 into openshift:master Sep 27, 2018
@openshift-ci-robot
Copy link
Contributor

@paulfantom: Updated the following 3 configmaps:

  • ci-operator-openshift-cluster-api-provider-libvirt configmap using the following files:
    • key master.yaml using file ci-operator/config/openshift/cluster-api-provider-libvirt/master.yaml
  • ci-operator-openshift-machine-api-operator configmap using the following files:
    • key master.yaml using file ci-operator/config/openshift/machine-api-operator/master.yaml
  • ci-operator-openshift-cluster-api-provider-aws configmap using the following files:
    • key master.yaml using file ci-operator/config/openshift/cluster-api-provider-aws/master.yaml

In response to this:

Propagate #1676.

/assign @enxebre @spangenberg

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.

@paulfantom paulfantom deleted the confidence branch November 29, 2018 13:11
wking added a commit to wking/openshift-release that referenced this pull request Apr 13, 2022
…fig: Bot doesn't need lgtm or approval

We trust it, and it's no longer authorized to add its own labels:

  * FAILED channels/fast-4.7: Promote 4.7.48. It was promoted to the
    feeder fast by 3ea452a650 (Merge pull request openshift#1745 from
    openshift/promote-4.7.48-to-fast, 2022-04-13) 1:39:00.240438
    ago. 403 {"message": "Must have admin rights to Repository.",
    "documentation_url":
    "https://docs.github.com/rest/reference/issues#add-labels-to-an-issue"}

Also drop the backport business for all authors, because we don't have
release branches in this repository.

I'd also like to drop bugzilla/invalid-bug, because we don't tie
changes to bugs.  But CI presubmits didn't like that [1]:

  {"component":"checkconfig","file":"k8s.io/test-infra/prow/cmd/checkconfig/main.go:90","func":"main.reportWarning","level":"warning","msg":"the following orgs or repos enable the bugzilla plugin but do not forbid the bugzilla/invalid-bug label for merging: [repo: openshift/cincinnati-graph-data]","severity":"warning","time":"2022-04-13T18:08:18Z"}

I poked around a bit trying to find a way to drop the Bugzilla plugin
from the graph-data repo, but couldn't find the incantation, so for
now I'm keeing the invalid-bug label in these queries.

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/27826/pull-ci-openshift-release-master-config/1514304177340157952#1:build-log.txt%3A10
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. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants