-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Merged by Bors] - Not me ... us #2654
Conversation
I think that the new recommendation is just not to have an authors field at all, for various reasons (primarily deadnaming concerns, I think) Afaik it's no longer added by default by |
Ooh I dig it. Less boilerplate is good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm that the only lines removed were the authors
field.
@@ -258,9 +258,8 @@ To locally lint your files using the same workflow as our CI: | |||
|
|||
If you end up adding a new official Bevy crate to the `bevy` repo: | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still need to make sure the other metadata is correct - at github.com/bevyengine/bevy
as the url, etc.
(For example, benches
doesn't have that which is probably fine)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thats fair, but also a bit tangential. Feel free to create a new PR / issue 😄
bors r+ |
I don't see much of a reason at this point to boost my name over anyone elses. We are all Bevy Contributors.
I don't see much of a reason at this point to boost my name over anyone elses. We are all Bevy Contributors.