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.

Sign up for GitHub

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

Jump to bottom

refactor(fs): remove unused field for CompositeFS #7195

Merged
merged 1 commit into from
Jul 22, 2024
Merged

refactor(fs): remove unused field for CompositeFS #7195

merged 1 commit into from
Jul 22, 2024

Conversation

nikpivkin
Copy link
Contributor

@nikpivkin nikpivkin commented Jul 19, 2024 •
edited
Loading

Description

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've followed the conventions in the PR title.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

@nikpivkin nikpivkin marked this pull request as ready for review July 22, 2024 06:48
@knqyf263 knqyf263 added this pull request to the merge queue Jul 22, 2024
Merged via the queue into aquasecurity:main with commit 5f78ea4 Jul 22, 2024
14 checks passed
skahn007gl pushed a commit to skahn007gl/trivy that referenced this pull request Jul 23, 2024
@nikpivkin @skahn007gl
refactor(fs): remove unused field for CompositeFS (aquasecurity#7195)
418258f 
Signed-off-by: nikpivkin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@knqyf263 knqyf263 knqyf263 approved these changes

@DmitriyLewen DmitriyLewen Awaiting requested review from DmitriyLewen DmitriyLewen is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nikpivkin @knqyf263