-
Notifications
You must be signed in to change notification settings - Fork 43
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
Move org.yaml from test-infra to evolution repository #274
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maxgio92 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 |
I think we finally have a clean history @leogr. There was history related to the source repository test-infra to a directory wrongly named "distrubution" under config. |
@leogr I think we're ready to unhold this and consequently update related pipelines. WDYT? |
Signed-off-by: Michele Zuccala <[email protected]>
Following the example of https://github.com/falcosecurity/test-infra#create-a-presubmits-job-that-runs-tests-on-prs and falcosecurity/test-infra#515. Signed-off-by: Mark Stemm <[email protected]>
He deserves it :) Signed-off-by: Mark Stemm <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Co-authored-by: Federico Di Pierro <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Massimiliano Giovagnoli <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
This is an emergency commit. The peribolos job is failing because the missing user "danpopnyc" (he has left the org :( ) Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Issif <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
…ners lists. Signed-off-by: Federico Di Pierro <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
So we can add him as a reviewer. See falcosecurity/falco#2137 Signed-off-by: Leonardo Grasso <[email protected]>
The maintainer expressed willingness to be removed from all repositories and the organization. See falcosecurity/falco#2122 Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Logan Bond <[email protected]>
Signed-off-by: Melissa Kilby <[email protected]>
Signed-off-by: Massimiliano Giovagnoli <[email protected]>
Co-authored-by: Leonardo Grasso <[email protected]> Signed-off-by: maxgio92 <[email protected]>
Co-authored-by: Federico Di Pierro <[email protected]> Signed-off-by: maxgio92 <[email protected]>
The |
… team Signed-off-by: Jason Dellaluce <[email protected]>
@falcosecurity/evolution-maintainers this is up to date and ready to be reviewed. |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
@falcosecurity/evolution-maintainers is there something I can do here? |
Hey @maxgio92 I lost track of this sorry. Is anything else needed to make this work ready yet? @FedeDP @LucaGuerra could you help with this? |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh with Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue with Mark the issue as fresh with Provide feedback via https://github.com/falcosecurity/community. |
@poiana: Closed this PR. In response to this:
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-sigs/prow repository. |
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area utils
What this PR does / why we need it:
As the evolution repository is now the central point for the evolution of the project, and as the falcosecurity organization is formed by the community, and as the point of contact of the contributions are in git (Github), is correct that the source of truth as a declarative configuration of the Github organization is put here.
Moreover, this PR adds the Prow job needed for the automation that reconciles the desired source of truth with the actual one.
Which issue(s) this PR fixes:
Fixes #176
Supersedes #204
/cc @leogr