@FraserGreenroyd to confirm, the following checks are now queued:
- `code-compliance`
- `documentation-compliance`
- `project-compliance`
- `branch-compliance`
- `dataset-compliance`
- `copyright-compliance`
There are 1 requests in the queue ahead of you.
@FraserGreenroyd to confirm, the following checks are now queued:
- `code-compliance`
- `documentation-compliance`
- `project-compliance`
- `core`
- `null-handling`
- `serialisation`
- `versioning`
- `installer`
The check `documentation-compliance` has already been run previously and recorded as a successful check. This check has not been run again at this time.
FAO: @FraserGreenroyd
@FraserGreenroyd is seeking dispensation on this Pull Request to skip a required check. Please can you provide authorisation for the check to be skipped, or provide assistance as appropriate.
The check they wish to have dispensation on is ready-to-merge.
If you are providing dispensation on this occasion, please reply with:
> @BHoMBot this is a DevOps instruction. I am authorising dispensation to be granted on check ref. `6129722289`
NOTE: Depends on
Issues addressed by this PR
Closes #220
Using BHoM Join instead of Rhino join to check if the curve can be coverted.
This is to avoid full blown crashes of Rhino from happening that can for some cases be triggered by the Rhino.Join method that was used.
Test files
https://burohappold.sharepoint.com/:f:/r/sites/BHoM/02_Current/12_Scripts/02_Pull%20Request/BHoM/Rhinoceros_Toolkit/%23221-AvoidCallingRhinoJoinToStopRhinoCrashWhenConvertingPolycurves?csf=1&web=1&e=UMB25Z
Changelog
Additional comments