Skip to content

Make the outputted "code generated" comment compatible with go generate#60

Open
NMFR wants to merge 2 commits into
cheekybits:masterfrom
NMFR:fix/change-output-comment-header
Open

Make the outputted "code generated" comment compatible with go generate#60
NMFR wants to merge 2 commits into
cheekybits:masterfrom
NMFR:fix/change-output-comment-header

Conversation

@NMFR

@NMFR NMFR commented Sep 20, 2019

Copy link
Copy Markdown

Go generate manual (go help generate) states:

To convey to humans and machine tools that code is generated,
generated source should have a line early in the file that
matches the following regular expression (in Go syntax):

	^// Code generated .* DO NOT EDIT\.$

This change modifies the generated header comment to match the description of go generate manual.

…ate` manual

Go generate manual (`go help generate`) states:
```
To convey to humans and machine tools that code is generated,
generated source should have a line early in the file that
matches the following regular expression (in Go syntax):

	^// Code generated .* DO NOT EDIT\.$
````

This change modifies the generated header comment to match the description of Go generate manual.
@NMFR NMFR changed the title Make the outputted "code generated" comment compatible with go generate manual Make the outputted "code generated" comment compatible with go generate Sep 20, 2019
@NMFR NMFR changed the title Make the outputted "code generated" comment compatible with go generate Make the outputted "code generated" comment compatible with go generate Sep 20, 2019

@xiegeo xiegeo left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless someone is depending on the old comment header, which they should not. I don't see why not.

@NMFR

NMFR commented Sep 24, 2019

Copy link
Copy Markdown
Author

Anything missing on my side to get this merged?

@ghostsquad

Copy link
Copy Markdown
Contributor

any movement on this?

@ghostsquad

Copy link
Copy Markdown
Contributor

@xiegeo any reason why this can't be merged?

@ghostsquad

Copy link
Copy Markdown
Contributor

this resolves #63

@xiegeo

xiegeo commented May 30, 2020

Copy link
Copy Markdown

@ghostsquad Sorry, I'm not a maintainer of this project so I don't have merging powers. I was doing a bunch of reviews requested and thought this was one of them.

@pdrum is the most recent maintainer that I know of.

@ghostsquad

Copy link
Copy Markdown
Contributor

Sad when valuable OSS projects go "dark". I had to start a release on my own fork until this is merged.

Maybe it's time to look for a new owner? @pdrum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants