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

Add boilerplate clean target for guardian #9948

Merged

Conversation

Brian-McM
Copy link
Contributor

Description

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

TBD

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

@Brian-McM Brian-McM requested a review from a team as a code owner March 7, 2025 16:37
@marvin-tigera marvin-tigera added this to the Calico v3.30.0 milestone Mar 7, 2025
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Mar 7, 2025
@caseydavenport caseydavenport added docs-not-required Docs not required for this change release-note-not-required Change has no user-facing impact labels Mar 7, 2025
@marvin-tigera marvin-tigera removed release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Mar 7, 2025
@caseydavenport
Copy link
Member

@Brian-McM is there nothing actually to clean here? Presumably we build something as part of this package :D

@Brian-McM
Copy link
Contributor Author

@Brian-McM is there nothing actually to clean here? Presumably we build something as part of this package :D

Ya there's probably things to clean, but for the moment to unblock hash releases this is an adequate. I can follow up at some other point to deal with this.

Comment on lines +99 to +100
clean:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I image at the very least, you will want this.

Suggested change
clean:
clean:
# Clean .created files which indicate images / releases have been built.
find . -name '.*.created*' -type f -delete
find . -name '.*.published*' -type f -delete
rm -rf bin

@Brian-McM Brian-McM merged commit 199c6d5 into projectcalico:master Mar 7, 2025
4 of 8 checks passed
@Brian-McM Brian-McM deleted the bm-fix-hash-release-for-guardian branch March 7, 2025 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required Docs not required for this change release-note-not-required Change has no user-facing impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants