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

Add oss-fuzz-ing #127

Open
1 task
06kellyjac opened this issue Dec 21, 2020 · 2 comments
Open
1 task

Add oss-fuzz-ing #127

06kellyjac opened this issue Dec 21, 2020 · 2 comments
Assignees
Labels
github_actions Pull requests that update Github_actions code good first issue
Projects

Comments

@06kellyjac
Copy link
Member

  • Add oss-fuzz actions

See here for docs https://google.github.io/oss-fuzz/getting-started/continuous-integration/#integrating-into-your-repository

@06kellyjac 06kellyjac self-assigned this Dec 21, 2020
@controlplane-bot controlplane-bot added this to To Do in Kubesec Dec 21, 2020
@06kellyjac 06kellyjac added the github_actions Pull requests that update Github_actions code label Dec 22, 2020
@JOSHUAJEBARAJ
Copy link

@06kellyjac Would like to pick up and work on Issue before starting with working on the issue I want to confirm few stuffs
I just need to add the yaml file under the workflows directory actions , If it is yes what should be the even trigger should It be the push or every pull request or something else

@06kellyjac
Copy link
Member Author

It can probably have triggers like this, every change to master and PR that has golang related changes
https://github.com/controlplaneio/kubesec/blob/master/.github/workflows/test_unit.yml#L5-L17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions Pull requests that update Github_actions code good first issue
Projects
Kubesec
  
To Do
Development

No branches or pull requests

2 participants