docs: add armen vardanyan to GDE resources

[Armenvardanyan95]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. 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.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[petebacondarwin]

@Armenvardanyan95 - I approved the content from a technical point of view (i.e. I checked the github and twitter accounts).

Please can you fix the image size:

Error: The following pictures exceed maximum size limit of 30kb:
  - /home/circleci/ng/aio/content/images/bios/armen-vardanyan.jpg

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. 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.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[Armenvardanyan95]

@petebacondarwin thanks for the notice, I reduced the image size

[petebacondarwin]

Thanks @Armenvardanyan95 - please can you squash the three commits into one - or if you want to keep three, make the second two commits fixup commits.

Also it appears that there is still a problem with your CLA signature.

[twerske]

LGTM once Pete's comments are fixed

[Armenvardanyan95]

@petebacondarwin I will squash the commits, but want to know how to fix the cla problem. Apparently I committed using my work mail instead of my personal mail, do I rebase my commits and change the email address on the commits?

[petebacondarwin]

@Armenvardanyan95 - I think the best way is to squash the commits into one, then manually update the commit author on this commit to the same email address that you are logged into Github. So something like:

git fetch upstream master
git rebase -i upstream/master
# mark the 2nd and 3rd commits as fixups
git commit --amend --author="John Doe <john@doe.org>"
git push --force-with-lease

[Armenvardanyan95]

@petebacondarwin thanks for guidance, done, now there is only one commit with the correct email ✔️

[petebacondarwin]

Thanks for sorting out the CLA problem @Armenvardanyan95.
Can you do one final rebase on the upstream master to trigger the CI to run?
Thanks!

[Armenvardanyan95]

@petebacondarwin sorry I somehow missed your comment
I didn't quite get that, how I should do it?

[petebacondarwin]

Hi @Armenvardanyan95 - no problem. This is what I would recommend...

Let's assume that you have a "git remote" set up that points the main angular/angular repo called upstream.
Then you could do:

git fetch upstream master
git checkout docs/contributors-gde-armenvardanyan
git rebase upstream/master
git push --force-with-lease

Or if you wanted to also update your local master branch as well (and if it was already tied to the upstream remote) you could simply do:

git checkout master
git pull
git checkout docs/contributors-gde-armenvardanyan
git rebase master
git push --force-with-lease

[AndrewKushnir]

FYI, I've pushed a rebase and if the CI is "green", we should be able to proceed with the merge.

[AndrewKushnir]

This PR was merged into the repository by commit 130f06e.

[Armenvardanyan95]

@AndrewKushnir thank you!

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}