Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

NMFR
Copy link

@NMFR NMFR commented Sep 20, 2019

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
Copy link

@xiegeo xiegeo left a comment

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
Copy link
Author

NMFR commented Sep 24, 2019

Anything missing on my side to get this merged?

@ghostsquad
Copy link
Contributor

any movement on this?

@ghostsquad
Copy link
Contributor

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

@ghostsquad
Copy link
Contributor

this resolves #63

@xiegeo
Copy link

xiegeo commented May 30, 2020

@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
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