This pr is only used to check the test method.
Comment From: weixsun
@wilkinsona I have checked all the test cases and erased them. You can take time to review them again. In addition, I created a new branch based on the older main branch, so there is a file MetricsHealthMicrometerExportTests conflict, can you help me deal with it?
Comment From: weixsun
There are many files whose year in the license header has not been updated. Is it okay to not update it?
😅 I forgot about it. It must be updated, let me make a quick change
Comment From: philwebb
@cuspymd For future reference, we don't require pull-requests to be 100% perfect and it's fine if things like copyright headers aren't updated. We don't want to put people off contributing. We'll generally fix that kind of thing up during the merge.
Comment From: cuspymd
@philwebb Thanks for responding. I also find it very inefficient to change the license header. It seems that policies related to this are different for each spring-project. For example spring-framework guides license update in coding style guide. There seems to be no explicit guide for contribution or coding style in spring-boot.
Comment From: snicoll
@cuspymd the coding style guide in spring framework is mostly intended to the team. We don't expect contributors to read and apply all these rules. As Phil mentioned, we're happy to fine tune formatting and conventions and don't expect PRs to be 100% perfect. In short, the review you did above isn't necessary, thank you.
Comment From: snicoll
Thanks again @weixsun
Comment From: cuspymd
@snicoll Thanks for the explanation. In the future, I will not review the coding style.