Exclude CVN in the code and fcl files for now - #627
Merged
bear-is-asleep merged 15 commits intoFeb 7, 2025
Conversation
…clFixesForv10 Fixing Fcls for the New Geometry Handling
Co-authored-by: Bear Carlson <bcarlson1@ufl.edu>
Co-authored-by: Bear Carlson <bcarlson1@ufl.edu>
…emoveGalleryFromCI Removing Gallery From CI
henrylay97
approved these changes
Feb 5, 2025
henrylay97
left a comment
Member
There was a problem hiding this comment.
This looks sensible for now with a revert as soon as the larsoft level issue is fixed.
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Exclude CVN in the code and fcl files for now.
Changes needed until lardnn issue is resolved - link
Checklist
Reviewers,AssigneesDevelopementRelevant PR links (optional)
Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?
No
Link(s) to docdb describing changes (optional)
Is there a docdb describing the issue this solves or the feature added?
No