Skip to content

Quick color check to qc#1920

Open
joshqsumner wants to merge 2 commits into
v5.0from
quick_color_check-to-qc
Open

Quick color check to qc#1920
joshqsumner wants to merge 2 commits into
v5.0from
quick_color_check-to-qc

Conversation

@joshqsumner
Copy link
Copy Markdown
Contributor

Describe your changes
Moving quick_color_check to qc submodule from transform

Type of update
This is a restructuring pr.

Associated issues
Part of #1910

Additional context
See #1910

For the reviewer
See this page for instructions on how to review the pull request.

  • PR functionality reviewed in a Jupyter Notebook
  • All tests pass
  • Test coverage remains 100%
  • Documentation tested
  • New documentation pages added to plantcv/mkdocs.yml
  • Changes to function input/output signatures added to updating.md
  • Code reviewed
  • PR approved

@joshqsumner joshqsumner changed the base branch from main to v5.0 May 12, 2026 19:36
@deepsource-io
Copy link
Copy Markdown

deepsource-io Bot commented May 12, 2026

DeepSource Code Review

We reviewed changes in 38b01e4...cd3200f on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Coverage  

Code Review Summary

Analyzer Status Updated (UTC) Details
Python May 12, 2026 8:14p.m. Review ↗
Code coverage May 12, 2026 8:14p.m. Review ↗

Code Coverage Summary

Language Line Coverage (New Code) Line Coverage (Overall)
Aggregate
100%
[✓ above threshold]
99.9%
[▼ down 0.1% from main]
Python
100%
[✓ above threshold]
99.9%
[▼ down 0.1% from main]

➟ Additional coverage metrics may have been reported. See full coverage report ↗


Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@joshqsumner joshqsumner added this to the PlantCV v5.0 milestone May 12, 2026
@joshqsumner joshqsumner added the merge in order Set of PRs that need to be merged sequentially label May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge in order Set of PRs that need to be merged sequentially ready to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant