<?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: Maxim Dzyubak</title>
    <description>The latest articles on DEV Community by Maxim Dzyubak (@maxdzyubak).</description>
    <link>https://dev.to/maxdzyubak</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%2F1095271%2Ff1a2bcb3-be42-4ba6-acdf-072fe8f4db08.jpeg</url>
      <title>DEV Community: Maxim Dzyubak</title>
      <link>https://dev.to/maxdzyubak</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/maxdzyubak"/>
    <language>en</language>
    <item>
      <title>How to commits to open source in GitHub. Step-by-step guide</title>
      <dc:creator>Maxim Dzyubak</dc:creator>
      <pubDate>Sun, 04 Jun 2023 14:17:52 +0000</pubDate>
      <link>https://dev.to/maxdzyubak/how-to-commits-to-open-source-in-github-step-by-step-guide-25n6</link>
      <guid>https://dev.to/maxdzyubak/how-to-commits-to-open-source-in-github-step-by-step-guide-25n6</guid>
      <description>&lt;p&gt;The guides are written for the &lt;a href="https://github.com"&gt;github&lt;/a&gt; service. You need to log in to your account or sign up.&lt;/p&gt;

&lt;p&gt;All commands in these guides are entered in the &lt;strong&gt;terminal&lt;/strong&gt;.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Make a &lt;strong&gt;fork&lt;/strong&gt; (copy) of the desired project. Go to your account and go to the just created fork.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Clone&lt;/strong&gt; the fork (copy) of the project from step 1 to your computer.&lt;br&gt;
Example:&lt;br&gt;
&lt;code&gt;git clone git@github.com:maxdzyubak/vite.git&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Configure the git config locally (&lt;strong&gt;local&lt;/strong&gt;). It must be repeated for each project:&lt;br&gt;
&lt;code&gt;git config --local user.name maxdzyubak&lt;/code&gt;&lt;br&gt;
&lt;code&gt;git config --local user.email maxdzyubak@gmail.com&lt;/code&gt;&lt;br&gt;
Or &lt;strong&gt;global&lt;/strong&gt;. Set up once for all projects&lt;br&gt;
&lt;code&gt;git config --global user.name maxdzyubak&lt;/code&gt;&lt;br&gt;
&lt;code&gt;git config --global user.email maxdzyubak@gmail.com&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;We make a pointer to the &lt;strong&gt;original upstream repository&lt;/strong&gt; from which we made the fork. This is needed to download the latest code updates from the original repository. (Checking upstream: &lt;code&gt;git remote -v&lt;/code&gt;).&lt;br&gt;
Example:&lt;br&gt;
&lt;code&gt;git remote add upstream https://github.com/vitejs/vite.git&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a new branch and go straight to it. Make all changes there. &lt;strong&gt;This is considered good practice&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;git switch -c new_branch&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You can check the status of changes made with the command&lt;br&gt;
&lt;code&gt;git status&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add the changes to &lt;strong&gt;staged&lt;/strong&gt;. Git starts tracking changes to the file(s)&lt;br&gt;
&lt;code&gt;git add README.md&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Make a commit with the changes. If there is an issue number, the best way to commit is to write it like this: &lt;strong&gt;[#123] fix bug&lt;/strong&gt;. If you just put a grid without parentheses, it will ignore it in the git rebase&lt;br&gt;
&lt;code&gt;git commit -m 'Update README.md'&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Check the commit made&lt;br&gt;
&lt;code&gt;git log&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Push the changes made to the outside world, because for now they are only on our local computer, indicating the created branch&lt;br&gt;
&lt;code&gt;git push origin new_branch&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a &lt;strong&gt;pull request&lt;/strong&gt; by clicking on the green button labeled &lt;strong&gt;Compare &amp;amp; pull request&lt;/strong&gt; either in the original repository from which you made the fork, or locally in our github account.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;Docs:&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-clone"&gt;git-clone - Clone a repository into a new directory&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration"&gt;Customizing Git - Git Configuration&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-remote#Documentation/git-remote.txt-emaddem"&gt;git-remote - Manage set of tracked repositories&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging"&gt;Git Branching - Basic Branching and Merging&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-status"&gt;git-status - Show the working tree status&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-add"&gt;git-add - Add file contents to the index&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-commit"&gt;git-commit - Record changes to the repository&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-log"&gt;git-log - Show commit logs&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-push"&gt;git-push - Update remote refs along with associated objects&lt;/a&gt;&lt;br&gt;
&lt;a href="https://git-scm.com/docs/git-request-pull"&gt;git-request-pull - Generates a summary of pending changes&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>beginners</category>
      <category>guide</category>
    </item>
  </channel>
</rss>
