| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
added disclaimer for beginning users
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it. What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
Sorry, something went wrong.
|
I signed it
…________________________________
From: googlebot <notifications@github.com>
Sent: Friday, August 28, 2020 5:03 AM
To: angular/angular.js <angular.js@noreply.github.com>
Cc: Steven Rugg <Steven.rugg@outlook.com>; Author <author@noreply.github.com>
Subject: Re: [angular/angular.js] Added disclaimer in the first paragraph to beginning users. (#17068)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
________________________________
What to do if you already signed the CLA
Individual signers
* It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>.
Corporate signers
* Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot<http://go/cla#troubleshoot> (Public version<https://opensource.google/docs/cla/#troubleshoot>).
* The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>.
* The email used to register you as an authorized contributor must also be attached to your GitHub account<https://github.com/settings/emails>.
ℹ️ Googlers: Go here<https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fangular%2Fangular.js%2Fpull%2F17068> for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#17068 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKPPUDAQSI2EYZSDHMT5GJDSC6MI7ANCNFSM4QOBXWZA>.
|
Sorry, something went wrong.
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Sorry, something went wrong.
|
@googlebot I signed it
…________________________________
From: googlebot <notifications@github.com>
Sent: Friday, August 28, 2020 5:03 AM
To: angular/angular.js <angular.js@noreply.github.com>
Cc: Steven Rugg <Steven.rugg@outlook.com>; Author <author@noreply.github.com>
Subject: Re: [angular/angular.js] Added disclaimer in the first paragraph to beginning users. (#17068)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
________________________________
What to do if you already signed the CLA
Individual signers
* It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>.
Corporate signers
* Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot<http://go/cla#troubleshoot> (Public version<https://opensource.google/docs/cla/#troubleshoot>).
* The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>.
* The email used to register you as an authorized contributor must also be attached to your GitHub account<https://github.com/settings/emails>.
ℹ️ Googlers: Go here<https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fangular%2Fangular.js%2Fpull%2F17068> for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#17068 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKPPUDAQSI2EYZSDHMT5GJDSC6MI7ANCNFSM4QOBXWZA>.
|
Sorry, something went wrong.
|
|
||
| # PhoneCat Tutorial App | ||
|
|
||
| *** This tutorial assumes that the reader has a basic knowledge of HTML, CSS and Javascript. If you have no |
There was a problem hiding this comment.
| *** This tutorial assumes that the reader has a basic knowledge of HTML, CSS and Javascript. If you have no | |
| *** This tutorial assumes that the reader has a fundamental knowledge of HTML, CSS, and JavaScript. If you have no |
Sorry, something went wrong.
| # PhoneCat Tutorial App | ||
|
|
||
| *** This tutorial assumes that the reader has a basic knowledge of HTML, CSS and Javascript. If you have no | ||
| experience coding or have not been introduced to Javascript, we highly suggest that you take some time |
There was a problem hiding this comment.
| experience coding or have not been introduced to Javascript, we highly suggest that you take some time | |
| experience coding or have not been introduced to JavaScript, we highly suggest that you take some time |
Sorry, something went wrong.
|
|
||
| *** This tutorial assumes that the reader has a basic knowledge of HTML, CSS and Javascript. If you have no | ||
| experience coding or have not been introduced to Javascript, we highly suggest that you take some time | ||
| to learn the basics of Javascript by going to https://www.javascript.com/learn/strings or |
There was a problem hiding this comment.
| to learn the basics of Javascript by going to https://www.javascript.com/learn/strings or | |
| to learn the basics of JavaScript by going to [MDN's JavaScript guide](https://developer.mozilla.org/en-US/docs/Web/JavaScript). |
Sorry, something went wrong.
| *** This tutorial assumes that the reader has a basic knowledge of HTML, CSS and Javascript. If you have no | ||
| experience coding or have not been introduced to Javascript, we highly suggest that you take some time | ||
| to learn the basics of Javascript by going to https://www.javascript.com/learn/strings or | ||
| https://www.w3schools.com/js/. *** |
There was a problem hiding this comment.
| https://www.w3schools.com/js/. *** |
Sorry, something went wrong.
|
Also from CI: Invalid commit message, please fix: - <subject> must not end with a dot Commit message was: docs(tutorial/Tutorial): describe your change... added disclaimer for beginning users See https://bit.ly/angular-guidelines You can find more at https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#commits |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
added disclaimer for beginning users
AngularJS is in LTS mode
We are no longer accepting changes that are not critical bug fixes into this project.
See https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c for more detail.
Does this PR fix a regression since 1.7.0, a security flaw, or a problem caused by a new browser version?
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements
Other information: