diff options
| author | drclaw1394 <drclaw@mac.com> | 2020-01-07 16:30:27 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-07 16:30:27 +1000 |
| commit | 896b7ced42b40eb3ee62c38d237d4d07df51f169 (patch) | |
| tree | 73af7aec5c7a251f6f5030fa9a7e39ae412af123 /README.md | |
| parent | 7649e23d2b150b36cdd134bcf17125f3b9696ada (diff) | |
| parent | e015238170e27c690e4f46646b6687f600fd0c59 (diff) | |
| download | perlweeklychallenge-club-896b7ced42b40eb3ee62c38d237d4d07df51f169.tar.gz perlweeklychallenge-club-896b7ced42b40eb3ee62c38d237d4d07df51f169.tar.bz2 perlweeklychallenge-club-896b7ced42b40eb3ee62c38d237d4d07df51f169.zip | |
Merge pull request #41 from manwar/master
Update to w42
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 74 |
1 files changed, 37 insertions, 37 deletions
@@ -5,15 +5,15 @@ This is the central repository for the members of [**Perl Weekly Challenge**](ht ## How to contribute? Just submit Pull Request with your solutions. -First find out the latest challenge folder, more likely the highest numbered folder is the latest challenge folder e.g. challenge-002. If you are an existing member, you would probably find a folder by your name. For example, if your name is "Joe Blog" then there would be a folder called "joe-blog". Under your named folder, you would find a file **README**. Depending on your choice of language, you should create a folder here e.g. **perl5** for Perl 5 and **perl6** for Perl 6. Inside each of these folders you can save your solutions. If it is perl5 script for challenge 1 then call it **ch-1.pl**. Similarly if it is perl5 script for challenge 2 then call it **ch-2.pl**. For perl6 solutions, call it **ch-1.p6** and **ch-2.p6** respectively. And if you are writing one-liner then call it **ch-1.sh** or **ch-2.sh**. If you are contributing for the first time, please create your named folder as described above. Also let us know what name you would like us to use? +First find out the latest challenge folder, more likely the highest numbered folder is the latest challenge folder e.g. challenge-002. If you are an existing member, you would probably find a folder by your name. For example, if your name is "Joe Blog" then there would be a folder called "joe-blog". Under your named folder, you would find a file **README**. Depending on your choice of language, you should create a folder here e.g. **perl** for **Perl** and **raku** for **Raku**. Inside each of these folders you can save your solutions. If it is perl script for **Task #1** then call it **ch-1.pl**. Similarly if it is perl script for **Task #2** then call it **ch-2.pl**. For **Raku** solutions, call it **ch-1.p6** and **ch-2.p6** respectively. And if you are writing one-liner then call it **ch-1.sh** or **ch-2.sh**. If you are contributing for the first time, please create your named folder as described above. Also let us know what name you would like us to use? In case you have created a blog about your solutions, then create a file called **blog.txt** and add the link to it. ## Step-by-step instructions -Let us assume you want to submit solutions for **Challenge 002** and your Github user name is **joe-blog**. +Let us assume you want to submit solutions for **Challenge 002** and your Github user name is **joe-blog**. 1. If you are submitting the solution for the first time then you have to **Fork** the repository **https://github.com/manwar/perlweeklychallenge-club** by clicking the "Fork" button in the top right corner and should have repository e.g. **https://github.com/joe-blog/perlweeklychallenge-club**. - + 2. Go to your favourite terminal and **clone** your repository. e.g **git clone https://github.com/joe-blog/perlweeklychallenge-club**. 3. Create a new branch for the solution **git checkout -b new-branch**. @@ -26,9 +26,9 @@ Let us assume you want to submit solutions for **Challenge 002** and your Github 6. If you just created the folder then you should add a file **README** and add a line **Solution by Joe Blog** otherwise skip to next step. -7. If you want to submit **Perl 5** solutions then you should create a folder **perl5** (if not already created). Similarly if you want to submit **Perl 6** solutions then you should create a folder **perl6** (if not already created). +7. If you want to submit **Perl 5** solutions then you should create a folder **perl** (if not already created). Similarly if you want to submit **Raku** solutions then you should create a folder **raku** (if not already created). -8. Change into your relevant folder depending on your choice **cd perl5** or **cd perl6**. +8. Change into your relevant folder depending on your choice **cd perl** or **cd raku**. 9. Now you are ready to add your solutions. If it is for the first challenge then create a file named **ch-1.pl** or **ch-1.p6** or **ch-1.sh**. Similarly, if it is for the second challenge then create a file named **ch-2.pl** or **ch-2.p6** or **ch-2.sh**. @@ -50,12 +50,12 @@ Let us assume you already have a fork. If this is the first time you are using t ``` $ git checkout master ``` - + 2. Check if you have setup **upstream**. ``` $ git remote -v ``` - + You should see something similar: ``` origin https://github.com/joe-blog/perlweeklychallenge-club (fetch) @@ -63,88 +63,88 @@ Let us assume you already have a fork. If this is the first time you are using t upstream https://github.com/manwar/perlweeklychallenge-club (fetch) upstream https://github.com/manwar/perlweeklychallenge-club (push) ``` - + If you don't see **upstream** as above then you need to setup your **upstream** like below: - + ``` $ git remote add upstream https://github.com/manwar/perlweeklychallenge-club ``` - + Check if you have everything setup correctly. - + ``` $ git remote -v ``` - + If you see similar output as above then you have setup **upstream** correctly. You only need to do it **once**. - + 3. Now we need to **fetch** latest changes from the **upstream**. ``` $ git fetch upstream ``` - + 4. We will now merge the changes into your local **master** branch. ``` $ git merge upstream/master --ff-only ``` - + 5. Then push your **master** changes back to the repository. ``` $ git push -u origin master ``` - + 6. Now it is time create new branch for new challenge ``` $ git checkout -b branch-for-challenge-005 ``` - + 7. Once you have a new **branch** ready, you can start adding your solutions or blog information. - + ``` $ cd challenge-005/joe-blog - + $ echo "URL to the blog" > blog.txt - - $ mkdir perl5 - - $ cd perl5 - + + $ mkdir perl + + $ cd perl + Add script like ch-1.pl or ch-2.pl or ch-1.sh or ch-2.sh - - $ mkdir perl6 - - $ cd perl6 - + + $ mkdir raku + + $ cd raku + Add script like ch-1.p6 or ch-2.p6 or ch-1.sh or ch-2.sh ``` - + Test your script now. - + 8. Commit your changes. ``` $ git add challenge-005/joe-blog - + $ git commit ``` - + 9. Now push the newly created branch **branch-for-challenge-005** ``` $ git push -u origin branch-for-challenge-005 ``` - + 10. Time to submit your changes as **Pull Request**. Go to GitHub web profile - + https://github.com/joe-blog/perlweeklychallenge-club - + You should see button to create **Pull Request**. - + If you have any trouble with the above instructions then please get in touch with me anytime <mohammad.anwar@yahoo.com>. |
