Skip to content

chore: restrict packages-preview-release job to current repo only #7343

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

Merged
merged 1 commit into from
Apr 14, 2025

Conversation

ruibaby
Copy link
Member

@ruibaby ruibaby commented Apr 14, 2025

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Restrict packages-preview-release job to current repo only

Does this PR introduce a user-facing change?

None

@f2c-ci-robot f2c-ci-robot bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. release-note-none Denotes a PR that doesn't merit a release note. labels Apr 14, 2025
@f2c-ci-robot f2c-ci-robot bot requested review from JohnNiang and wan92hen April 14, 2025 10:27
Copy link

codecov bot commented Apr 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.47%. Comparing base (60c2009) to head (80dfaf3).
Report is 12 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #7343      +/-   ##
============================================
+ Coverage     57.18%   57.47%   +0.28%     
- Complexity     4066     4107      +41     
============================================
  Files           721      723       +2     
  Lines         24546    24670     +124     
  Branches       1612     1634      +22     
============================================
+ Hits          14036    14178     +142     
+ Misses         9882     9842      -40     
- Partials        628      650      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@JohnNiang JohnNiang left a comment

Choose a reason for hiding this comment

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

/lgtm

@f2c-ci-robot f2c-ci-robot bot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2025
Copy link

f2c-ci-robot bot commented Apr 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JohnNiang

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

@f2c-ci-robot f2c-ci-robot bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2025
@ruibaby ruibaby merged commit e8867a0 into halo-dev:main Apr 14, 2025
9 checks passed
@ruibaby ruibaby deleted the refine-packages-preview branch April 14, 2025 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants