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

Move org.yaml to evolution repo #840

Open
2 tasks
maxgio92 opened this issue Sep 6, 2022 · 16 comments
Open
2 tasks

Move org.yaml to evolution repo #840

maxgio92 opened this issue Sep 6, 2022 · 16 comments
Labels
enhancement New feature or request

Comments

@maxgio92
Copy link
Member

maxgio92 commented Sep 6, 2022

This is the mirror issue of falcosecurity/evolution#176.

Motivation

As the evolution repository is now the central point for the evolution of the project and its ecosystem, 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 in the evolution repository.

Feature

Alternatives

Additional context
cc @falcosecurity/evolution-maintainers

@maxgio92
Copy link
Member Author

maxgio92 commented Sep 6, 2022

I propose to adopt in-repo-config, so that the Peribolos ProwJob is configured in the same place the code is in (i.e. the org.yaml Github organization configuration file, in the evolution repository).

Furthermore, this way, we can ensure the job is triggered, both when:

  • the org.yaml file changes
  • the job config changes.

E.g. the job config could be something like that:

postsubmits:
  falcosecurity/evolution:
    - name: peribolos-post-submit
      branches:
        - ^master$
      decorate: true
      run_if_changed: '^people/org.yaml$|^.prow/peribolos.yaml$'
      ...

/cc @zuc @leogr

@poiana
Copy link
Contributor

poiana commented Jan 17, 2023

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

@maxgio92
Copy link
Member Author

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Apr 17, 2023

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

@maxgio92
Copy link
Member Author

/remove-lifecycle stale

@maxgio92 maxgio92 added the enhancement New feature or request label May 16, 2023
@poiana
Copy link
Contributor

poiana commented Oct 20, 2023

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

@poiana
Copy link
Contributor

poiana commented Nov 19, 2023

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

@poiana
Copy link
Contributor

poiana commented Dec 19, 2023

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
Copy link
Contributor

poiana commented Dec 19, 2023

@poiana: Closing this issue.

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/test-infra repository.

@poiana poiana closed this as completed Dec 19, 2023
@leogr
Copy link
Member

leogr commented Dec 20, 2023

/remove-lifecycle rotten

We still want this

@leogr leogr reopened this Dec 20, 2023
@poiana
Copy link
Contributor

poiana commented Mar 19, 2024

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

@leogr
Copy link
Member

leogr commented Mar 22, 2024

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Jun 20, 2024

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

@leogr
Copy link
Member

leogr commented Jun 20, 2024

/remove-lifecycle stale

@poiana
Copy link
Contributor

poiana commented Sep 18, 2024

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

@leogr
Copy link
Member

leogr commented Sep 20, 2024

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants