Is your feature request related to a problem? Please describe.
We are using odata-cli in command line into our pipeline flows.
The generated files always have a change on their headers with that line:
// Generation date: 26/05/2023 15:39:04
This produce lot of necessary noise to our developers.
Describe the solution you'd like
Have an option in odata-cli command line to not output generation date
Describe alternatives you've considered
Ignore the generated files from our VCS and only generated them on the fly.
Unfortunately we are working in .Net 7 and odata-cli is still not available in .Net 7, making all our flows more complex by doing that (even if it would be better).
That date is anyway redundant with our VCS history
Additional context
Here is a git diff view with the change:

Is your feature request related to a problem? Please describe.
We are using odata-cli in command line into our pipeline flows.
The generated files always have a change on their headers with that line:
// Generation date: 26/05/2023 15:39:04
This produce lot of necessary noise to our developers.
Describe the solution you'd like
Have an option in odata-cli command line to not output generation date
Describe alternatives you've considered
Ignore the generated files from our VCS and only generated them on the fly.
Unfortunately we are working in .Net 7 and odata-cli is still not available in .Net 7, making all our flows more complex by doing that (even if it would be better).
That date is anyway redundant with our VCS history
Additional context
Here is a git diff view with the change:
