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.

Sign up for GitHub

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

Jump to bottom

Add build job to github workflow #3

Open
chen-keinan opened this issue Jul 8, 2024 · 5 comments · May be fixed by #4
Open

Add build job to github workflow #3

chen-keinan opened this issue Jul 8, 2024 · 5 comments · May be fixed by #4
Assignees
@chen-keinan
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@chen-keinan
Copy link
Member

chen-keinan commented Jul 8, 2024 •
edited
Loading

Description

it is required to add build job to github workflow to validate:

  • formatting
  • lint
  • tidy
  • tests
@chen-keinan chen-keinan added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jul 8, 2024
@chen-keinan chen-keinan self-assigned this Jul 9, 2024
@chen-keinan chen-keinan linked a pull request Jul 9, 2024 that will close this issue
Open
@k8s-triage-robot
Copy link

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

This bot triages un-triaged 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:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2024
@k8s-triage-robot
Copy link

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:

  • 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 as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 6, 2024
@tabbysable
Copy link

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 18, 2024
@tabbysable
Copy link

Is there a reason to do this in github actions rather than Prow? For maintainability, I'd prefer we use Prow as much as possible.

@chen-keinan
Copy link
Member Author

Is there a reason to do this in github actions rather than Prow? For maintainability, I'd prefer we use Prow as much as possible.

Thanks for the feedback , I'll take a look at Prow and see how it can fit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chen-keinan chen-keinan

Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: add code build workflow chen-keinan/cve-feed-osv
4 participants
@chen-keinan @k8s-ci-robot @tabbysable @k8s-triage-robot