<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: @theekrystallee</title>
    <description>The latest articles on DEV Community by @theekrystallee (@theekrystallee).</description>
    <link>https://dev.to/theekrystallee</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F300459%2F68d6dc87-891f-41f4-aa02-cad547bcd789.jpeg</url>
      <title>DEV Community: @theekrystallee</title>
      <link>https://dev.to/theekrystallee</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/theekrystallee"/>
    <language>en</language>
    <item>
      <title>How to Get Testnet ETH and MATIC</title>
      <dc:creator>@theekrystallee</dc:creator>
      <pubDate>Wed, 10 Aug 2022 07:23:00 +0000</pubDate>
      <link>https://dev.to/theekrystallee/how-to-get-testnet-eth-and-matic-12l8</link>
      <guid>https://dev.to/theekrystallee/how-to-get-testnet-eth-and-matic-12l8</guid>
      <description>&lt;h2&gt;
  
  
  ETH
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Goerli Testnet&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A proof-of-authority testnet that works across clients; an ideal testnet for application developers. Goerli will be the final testnet merged to proof-of-stake before Ethereum Mainnet is merged. This is expected to happen in summer 2022. Goerli is expected to be maintained long term as a proof-of-stake testnet.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://goerli.etherscan.io/"&gt;Etherscan &lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Goerli Faucets&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://goerlifaucet.com/"&gt;Alchemy faucet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://faucets.chain.link/goerli"&gt;Chainlink faucet&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  MATIC
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Mumbai Testnet&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Mumbai testnet is the testnet of the Polygon network, which replicates the Polygon mainnet. It enables developers to deploy, test, and execute their dApps in the blockchain environment risk-free and at no cost. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://mumbai.polygonscan.com/"&gt;Polygonscan&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Mumbai Faucets&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://faucet.polygon.technology/"&gt;Polygon faucet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://mumbaifaucet.com/"&gt;Alchemy faucet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://faucets.chain.link/mumbai"&gt;Chainlink faucet&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Follow me on &lt;a href="https://twitter.com/theekrystallee"&gt;twitter&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>testing</category>
      <category>polygon</category>
      <category>ethereum</category>
    </item>
    <item>
      <title>How to Push Existing Repo to GitHub</title>
      <dc:creator>@theekrystallee</dc:creator>
      <pubDate>Tue, 09 Aug 2022 20:40:00 +0000</pubDate>
      <link>https://dev.to/theekrystallee/how-to-initialize-add-commit-and-push-your-local-project-repo-to-github-2456</link>
      <guid>https://dev.to/theekrystallee/how-to-initialize-add-commit-and-push-your-local-project-repo-to-github-2456</guid>
      <description>&lt;h3&gt;
  
  
  Introduction
&lt;/h3&gt;

&lt;p&gt;In this tutorial, you will learn how to push your locally hosted project code to GitHub.&lt;/p&gt;

&lt;h3&gt;
  
  
  Prerequisites
&lt;/h3&gt;

&lt;p&gt;To initialize your local repository and push it to GitHub, you will need:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;a href="https://github.com/" rel="noopener noreferrer"&gt;A GitHub account&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://git-scm.com/book/en/v2/Getting-Started-Installing-Git" rel="noopener noreferrer"&gt;Have &lt;code&gt;git&lt;/code&gt; installed on your local machine&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Create a new GitHub repo
&lt;/h3&gt;

&lt;p&gt;Sign into GitHub and create a new empty repo. &lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo6klit2eqw0zrtqwia51.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo6klit2eqw0zrtqwia51.png" alt="how to create a new repository page on GitHub"&gt;&lt;/a&gt; &lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Git Commands
&lt;/h3&gt;

&lt;p&gt;Run the following commands after navigating to the project folder you want to add and push to GitHub.&lt;/p&gt;

&lt;h4&gt;
  
  
  Initialize the Git repo
&lt;/h4&gt;

&lt;p&gt;Make sure you are in the root directory of the project you want to push to GitHub and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git init -b main
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This step creates a hidden &lt;code&gt;.git&lt;/code&gt; directory in your local project folder used to store all version history and metadata for the project.&lt;/p&gt;

&lt;h4&gt;
  
  
  Add and commit files
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git add . &amp;amp;&amp;amp; git commit -m "initial commit"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;git add&lt;/code&gt; command tells git which files to include in the commit. The &lt;code&gt;-A&lt;/code&gt; or &lt;code&gt;--all&lt;/code&gt; argument means "include all" files in that project folder.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;git commit&lt;/code&gt; command creates a new commit with all the files that have been added from the previous step. The &lt;code&gt;-m&lt;/code&gt; or &lt;code&gt;--message&lt;/code&gt; sets the commit message that will be included with the commit.&lt;/p&gt;

&lt;h4&gt;
  
  
  Check status
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git status
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;git status&lt;/code&gt; command displays what changes have been staged. In this case, you want to check that all files from your local project directory have been added. &lt;/p&gt;

&lt;h4&gt;
  
  
  Add new remote repo
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git remote add origin &amp;lt;GitHub repo link&amp;gt;
# sets the new remote

git remote -v
# verifies the new remote URL
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In git, "remote" refers to a remote version of the same repository, typically hosted on GitHub. "origin" is the default name git gives to a remote repo. &lt;code&gt;git remote add origin&lt;/code&gt; is telling git to add the URL of the default remote server for this repo.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;You can run the &lt;code&gt;git remote -v&lt;/code&gt; command to check that your GitHub repo was added as the remote repo that you will be pushing your local changes to. &lt;/p&gt;
&lt;/blockquote&gt;

&lt;h4&gt;
  
  
  Push to GitHub
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git push -u -f origin main
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;-u&lt;/code&gt; flag sets the remote &lt;code&gt;origin&lt;/code&gt; as the upstream reference that allows you to perform &lt;code&gt;git push&lt;/code&gt; and &lt;code&gt;git pull&lt;/code&gt; commands without specifying an &lt;code&gt;origin&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;-f&lt;/code&gt; flag stands for &lt;em&gt;force&lt;/em&gt; and will automatically overwrite everything in the remote directory. &lt;/p&gt;

&lt;h3&gt;
  
  
  All steps
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. git init
2. git add . &amp;amp;&amp;amp; git commit -m "initial commit"
3. git remote add origin &amp;lt;GitHub repo link&amp;gt;
4. git push -u -f origin main
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Conclusion
&lt;/h3&gt;

&lt;p&gt;Now you are all set to track your local code changes remotely in GitHub and understand the basics on how to add project files, commit changes, and push your code. The steps listed above are best for personal projects.&lt;/p&gt;

&lt;p&gt;Follow steps 2 and 4 to push your local code changes to your GitHub a couple of times an hour to avoid large commits.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where to Find Me
&lt;/h3&gt;

&lt;p&gt;Feel free to reach out to me with any questions on &lt;a href="https://twitter.com/theekrystallee" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt; and follow me on &lt;a href="https://www.tiktok.com/@theekrystallee" rel="noopener noreferrer"&gt;TikTok&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Happy building 🧱&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>github</category>
      <category>git</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
