Navigation Menu

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

Move authors assigner to required attributes section of Gem::Specification #2406

Merged
1 commit merged into from Sep 25, 2018
Merged

Move authors assigner to required attributes section of Gem::Specification #2406

1 commit merged into from Sep 25, 2018

Conversation

greysteil
Copy link
Contributor

Currently, the gem specification docs suggest that author / authors is a "recommended" attribute.

In fact, author / authors is a required attribute.

This PR is a code move that puts the authors assignment method into the required attributes section (and updates its description to explain that specifying author is an alternative). This should make the docs much clearer next time they're generated.

@bronzdoc
Copy link
Member

@bundlerbot r+

ghost pushed a commit that referenced this pull request Sep 25, 2018
2406: Move authors assigner to required attributes section of Gem::Specification r=bronzdoc a=greysteil

Currently, the [gem specification docs](https://guides.rubygems.org/specification-reference/) suggest that author / authors is a "recommended" attribute.

In fact, [author / authors is a required attribute](https://github.com/rubygems/rubygems/blob/master/lib/rubygems/specification_policy.rb#L287-L291).

This PR is a code move that puts the `authors` assignment method into the required attributes section (and updates its description to explain that specifying `author` is an alternative). This should make the docs much clearer next time they're generated.

Co-authored-by: Grey Baker <greysteil@gmail.com>
@ghost
Copy link

ghost commented Sep 25, 2018

Build succeeded

@ghost ghost merged commit 70a8c49 into rubygems:master Sep 25, 2018
This pull request was closed.
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.

None yet

3 participants