Skip to content

Conversation

leogr
Copy link
Member

@leogr leogr commented May 12, 2025

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area plugins

/area registry

/area build

/area documentation

What this PR does / why we need it:

# This nonce is used to force a CI job to re-run when no other meaningful changes are made.
# For example, this can be used to update the artifact index: https://github.com/falcosecurity/falcoctl/blob/gh-pages/index.yaml
# To trigger the job manually, update the number below (e.g., by replacing it with the current Unix timestamp).
# It does not need to be secure or unique beyond being different from the previous value.
# Example: `date +%s` on Unix-like systems will generate a suitable value.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
/hold

I will unhold when needed.

Signed-off-by: Leonardo Grasso <[email protected]>
@poiana
Copy link
Contributor

poiana commented May 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leogr

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana
Copy link
Contributor

poiana commented Aug 10, 2025

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 Sep 9, 2025

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

@leogr
Copy link
Member Author

leogr commented Sep 10, 2025

/remove-lifecycle rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants