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

Add CONTRIBUTING guidelines #317

Merged
merged 5 commits into from
Jun 29, 2016
Merged

Conversation

levithomason
Copy link
Member

@levithomason levithomason commented Jun 29, 2016

Fixes #314. This PR adds contributing guidelines and updates the README to account for those. Best to view the rendered versions:

CONTRIBUTING.md
README.md updated

@levithomason levithomason changed the title Add CONTRIBUTING doc Add CONTRIBUTING guidelines Jun 29, 2016
@codecov-io
Copy link

codecov-io commented Jun 29, 2016

Current coverage is 88.32%

Merging #317 into master will increase coverage by 0.01%

@@             master       #317   diff @@
==========================================
  Files            62         62          
  Lines           821        822     +1   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits            725        726     +1   
  Misses           96         96          
  Partials          0          0          

Powered by Codecov. Last updated by 1649cd4...574255e

@levithomason levithomason force-pushed the feature/how-to-write-a-component branch 3 times, most recently from 99be9a4 to 128a8a9 Compare June 29, 2016 20:00

### _meta

Every component has a static property called `_meta`. This object defines the component. The values here are used in `propTypes`, generated documentation, generated test cases, and some utilities.
Copy link
Member

Choose a reason for hiding this comment

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

Oh gross, the markdown is messed up in the diff from the _meta. Looks fine in the real renderer, though.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yea, never much luck with big diffs of markdown.

@dvdzkwsk
Copy link
Member

Mostly grammar fixes, 👻 other than that though, looks good.

@dvdzkwsk
Copy link
Member

Also, not sure if you want to include it, but since we abide by them....

https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit

@levithomason levithomason force-pushed the feature/how-to-write-a-component branch from 128a8a9 to d6d9215 Compare June 29, 2016 21:02
@levithomason levithomason force-pushed the feature/how-to-write-a-component branch 2 times, most recently from 93f7a50 to c3d83d9 Compare June 29, 2016 21:08
@levithomason
Copy link
Member Author

Added commit message format guidelines.

@levithomason levithomason force-pushed the feature/how-to-write-a-component branch 2 times, most recently from eca3137 to 574255e Compare June 29, 2016 21:41
@levithomason levithomason force-pushed the feature/how-to-write-a-component branch from 574255e to fab8de5 Compare June 29, 2016 21:56
@levithomason levithomason merged commit 88f86cf into master Jun 29, 2016
@levithomason levithomason deleted the feature/how-to-write-a-component branch June 29, 2016 21:57
jhchill666 pushed a commit to jhchill666/stardust that referenced this pull request Jul 5, 2016
* fix(webpack): remove cruft

* fix(Label): fix doc block grammar

* feat(package): add markdown toc with doctoc

* docs(contributing): add contributing doc

* refactor(readme): remove all dev info
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