Purpose readme contribution #13963
Purpose readme contribution #13963
Conversation
Add a new purpose section to enable newcomers (technical and non-technical) better understand the purpose of AngularJS
fix a few typos and reworded the example of reactive programmin.
docs:purpose-readme update
final update on purpose section added
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
|
I am the one who signed the CLA and authored the commits. I have added the associated email address into my Google account. Hope this resolves the conflict. Aashish From: googlebot [email protected] We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login herehttps://cla.developers.google.com/ to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. Reply to this email directly or view it on GitHubhttps://github.com//pull/13963#issuecomment-180982490. |
|
I apologize, I understood the message incorrectly. I will ask my colleague to complete and sign the CLA. |
|
@googlebot |
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
|
@googlebot |
|
Thanks guys! I squashed the changes into a single commit |
Add a new purpose section to enable newcomers (technical and non-technical) better understand the purpose of AngularJS Close #13963
Add a new purpose section to enable newcomers (technical and non-technical) better understand the purpose of AngularJS Close #13963
|
I am one of the commit authors Vito(@vitoahmeny) and I have signed the cla, please don't close the pull request due to cla issue. Thanks |
|
Thanks Pete @petebacondarwin for merging the changes into AngularJS README. Happy to contribute. 👍 @vitoahmeny, the request is closed as the changes have been accepted. 😄 |
|
That's great! 👍 |
To make AngularJS more approachable to a larger number of users — from informed developers to curious passers-by and new and interested visitors — I have added a new section to the AngularJS's README.md. The section is entitled What to Use AngularJS for and When to Use It. As the name suggests, the new section, a brief paragraph, explains in plain and straight-forward language what AngularJS is used for and when one should use it.
Other repositories may begin to use this new informative and catchy section soon, as my colleagues contact open-source technologies in an effort to make them more accessible to the tens of thousands of new users learning to code and thousands joining GitHub every day.
I hope you also find this section informative and useful enough to include this section for all future visitors to the repository.