org icon indicating copy to clipboard operation
org copied to clipboard
verified publisher icon kubernetes

REQUEST: enable codecov.io in kubernetes-sigs

Open marquiz opened this issue 4 years ago • 8 comments

Organization or Repo

kubernetes-sigs

Name of integration

codecov.io

Link to integration website

https://app.codecov.io/gh

Describe what is attempting to be accomplished

As a project maintainer, I'd like to be able to integrate codecov reports to Node Featgure Discovery

Additional context for request

No response

marquiz avatar Nov 05 '21 15:11 marquiz

I second that, also would like to have it enabled on the new repo https://github.com/kubernetes/org/issues/3140

zvonkok avatar Dec 09 '21 09:12 zvonkok

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

This bot triages issues and PRs 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:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Mar 09 '22 10:03 k8s-triage-robot

/remove-lifecycle stale

marquiz avatar Mar 09 '22 12:03 marquiz

ping @ameukam @cblecker @idvoretskyi @mrbobbytables @nikhita @palnabarun who could comment on this?

marquiz avatar May 04 '22 06:05 marquiz

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

This bot triages issues and PRs 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:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Aug 02 '22 06:08 k8s-triage-robot

/remove-lifecycle stale

marquiz avatar Aug 08 '22 13:08 marquiz

ping @ameukam @cblecker @idvoretskyi @mrbobbytables @nikhita @palnabarun

Any thoughts/comments?

marquiz avatar Aug 08 '22 13:08 marquiz

+1 for this.

qbarrand avatar Aug 23 '22 12:08 qbarrand

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

This bot triages issues and PRs 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:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Nov 21 '22 12:11 k8s-triage-robot

/remove-lifecycle stale

marquiz avatar Nov 21 '22 16:11 marquiz

@marquiz I assume you're still looking for this? Sorry for the delay on response.

cblecker avatar Nov 23 '22 23:11 cblecker

I assume you're still looking for this? Sorry for the delay on response.

Yeah, sure this is still valid 😊

marquiz avatar Nov 24 '22 08:11 marquiz

The GitHub authorization parts are set up. You can complete the setup at https://app.codecov.io/gh/kubernetes-sigs/node-feature-discovery/new

cblecker avatar Jan 15 '23 23:01 cblecker