Skip to content

Updating CODEOWNERS for wasm branch #6069

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Conversation

wileyj
Copy link
Collaborator

@wileyj wileyj commented May 2, 2025

use updated team name in codeowners

Copy link

codecov bot commented May 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.58%. Comparing base (0c11b86) to head (6e48b0c).
Report is 4 commits behind head on feat/clarity-wasm-develop.

❌ Your project status has failed because the head coverage (33.58%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@                      Coverage Diff                      @@
##           feat/clarity-wasm-develop    #6069      +/-   ##
=============================================================
- Coverage                      34.17%   33.58%   -0.60%     
=============================================================
  Files                            528      528              
  Lines                         392220   392220              
  Branches                         323      323              
=============================================================
- Hits                          134059   131710    -2349     
- Misses                        258153   260502    +2349     
  Partials                           8        8              

see 52 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c10dde4...6e48b0c. Read the comment docs.

🚀 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.

@wileyj wileyj requested review from obycode and csgui May 7, 2025 18:21
obycode
obycode previously approved these changes May 7, 2025
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

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

LGTM assuming you're planning to change the name after this merges?

@wileyj
Copy link
Collaborator Author

wileyj commented May 8, 2025

LGTM assuming you're planning to change the name after this merges?

yes...i'll have to adjust this PR to match the changes in develop

csgui
csgui previously approved these changes May 8, 2025
@wileyj wileyj dismissed stale reviews from csgui and obycode via 6e48b0c May 8, 2025 16:49
@wileyj wileyj added this pull request to the merge queue Jun 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to Branch Protection failures Jun 3, 2025
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@wileyj wileyj added this pull request to the merge queue Jun 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to Branch Protection failures Jun 3, 2025
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@wileyj wileyj added this pull request to the merge queue Jun 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to Branch Protection failures Jun 3, 2025
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@wileyj wileyj added this pull request to the merge queue Jun 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to Branch Protection failures Jun 3, 2025
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@wileyj wileyj added this pull request to the merge queue Jun 3, 2025
Merged via the queue into stacks-network:feat/clarity-wasm-develop with commit 5d83221 Jun 3, 2025
183 of 202 checks passed
@wileyj wileyj deleted the chore/clarity-wasm-codeowners branch June 3, 2025 16:47
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants