Use GPT-4 for code review

[ChaoticRoman]

• GPT-4 for code reviews

[github-actions]

The code change you've made is in the GitHub Actions workflow file, specifically in the code-review.yml file. You've added a new parameter to the gpt-code-review-action action, specifying the model as 'gpt-4'.

Here's my feedback:

1. Correctness: The code change seems syntactically correct assuming that 'gpt-4' is a valid model for the gpt-code-review-action.

2. Best Practices: It's good that you're using GitHub Secrets (${{ secrets.OPENAI_API_KEY }}) to securely store and use your OpenAI API Key.

3. Readability: The code change is small and straightforward, so it doesn't affect the overall readability.

4. Maintainability: The change is isolated and should not affect the maintainability of the code.

5. Performance: This change does not have any performance implications.

However, it's important to note that as of now, OpenAI has only released up to GPT-3 models. Unless you have access to a 'gpt-4' model or it's a placeholder for future use, this could potentially cause an error. Please verify the model name or check the documentation of the gpt-code-review-action to ensure that 'gpt-4' is a valid input.

[github-actions]

Prompt too long for OpenAI: 39539 characters, sending only first 4000 characters
The code changes seem to be well-structured and clean. Here are some observations:

1. In the code-review.yml file, you've added a model parameter to the GitHub Action. This is good if you want to specify a particular model for the code review action. However, please ensure that 'gpt-4' is a valid model for the gpt-code-review-action GitHub Action.

2. You've added comments to the CMakeLists.txt file, which is good for code readability.

3. In the CMakeLists.txt file, you've added a new package fmt using CPM.cmake. This is a good practice to manage dependencies in CMake. Just ensure that the version and repository of the package are correct.

4. You've added a new file CPM.cmake, which is a package manager for CMake. This is a good addition if your project has external dependencies. However, the diff is cut off at the end, so I can't review the entire file.

In general, the changes look good. Just make sure to test everything thoroughly to ensure the new configurations and dependencies work as expected.