-
Notifications
You must be signed in to change notification settings - Fork 14
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
Update Copyright Header to 2021 #2253
Conversation
@BHoMBot just to let you know, I have provided a |
1 similar comment
@BHoMBot just to let you know, I have provided a |
@BHoMBot check copyright compliance |
@FraserGreenroyd to confirm, |
@BHoMBot check copyright compliance |
@FraserGreenroyd to confirm, |
/azp run BHoM_Engine.CheckInstaller |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, would be good for at least one other review if possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested programmatically with this script. Two files need fixing:
BHoM_Engine\Spatial_Engine\Compute\MapDomain.cs
BHoM_Engine\Spatial_Engine\Modify\MapPositionDomain.cs
Both have a double copyright header.
Also worth mentioning that the following file has been flagged up for having a double copyright:
BHoM_Engine\Serialiser_Engine\Objects\MemberMapConventions\ImmutableBHoMCreatorMapConvention.cs
One is ours, one is MongoDB Inc since this is a file we copied from them. So might be better not to add our copyright on that one.
@BHoMBot check copyright compliance |
@FraserGreenroyd to confirm, |
/azp run BHoM_Engine.CheckInstaller |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reran the test and all looks good now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed the test @adecler has been using and it looks robust so will give this PR another couple of hours for other reviews and then will merge by 12PM UTC.
Closes #2252