falcosecurity
Move org.yaml from test-infra to evolution 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
[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
- ~~OWNERS~~ [maxgio92]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
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?
@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 /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/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? If yes, we should just schedule when. I would not say this is super urgent, but this issue has been open for too long, so I would address it.
@FedeDP @LucaGuerra could you help with this?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten.Provide feedback via https://github.com/falcosecurity/community. /close
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.