codegen: use standard header for generated files #1406
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use the standard header in generated Go sources. See https://go.dev/s/generatedcode.
|
#1338 already proposed that change. Mine also add references to the documentation of the standard. |
dolmen
force-pushed
the
use-std-header-for-generated-code
branch
from
e8c7a91 to
5ca0755
Compare
This was referenced Apr 26, 2024
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Modify _codegen to use the standard header in generated Go sources.
See https://go.dev/s/generatedcode.
Motivation
This enables editor support for blocking manual changes in generated sources.