From eee8beea761ff1a0b2cc4b22906c2554debe6cd5 Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Wed, 21 Aug 2019 11:09:37 +0100 Subject: Updated README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index ab6e064cf3..675493239e 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ In case you have created a blog about your solutions, then create a file called ## Step-by-step instructions Let us assume you want to subtmit 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 by clicking the "Fork" button in the top right corner and should have repository e.g. **https://github.com/joe-blog/perlweeklychallenge-club**. +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**. -- cgit From 40c16f1e4fca014f8e378db7f67ee14ab095ff4b Mon Sep 17 00:00:00 2001 From: Chason Deshotel Date: Thu, 21 Nov 2019 14:04:40 -0600 Subject: fixed typo, 'subtmit'->'submit' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 675493239e..dd56623e80 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ First find out the latest challenge folder, more likely the highest numbered fol 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 subtmit 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**. -- cgit From 8961b212ccc2489fa5c45e3882154e2ff52e9a6b Mon Sep 17 00:00:00 2001 From: Chason Deshotel Date: Thu, 21 Nov 2019 14:10:04 -0600 Subject: fixed typo 'branh'->'branch' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index dd56623e80..fe8288f9cf 100644 --- a/README.md +++ b/README.md @@ -133,7 +133,7 @@ Let us assume you already have a fork. If this is the first time you are using t $ git commit ``` -9. Now push the newly created branh **branch-for-challenge-005** +9. Now push the newly created branch **branch-for-challenge-005** ``` $ git push -u origin branch-for-challenge-005 -- cgit From 792d136647095d5cf5335c230d1091217db1e151 Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Sun, 29 Dec 2019 21:53:02 +0000 Subject: Updated README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index fe8288f9cf..4ac010f359 100644 --- a/README.md +++ b/README.md @@ -145,6 +145,6 @@ Let us assume you already have a fork. If this is the first time you are using t https://github.com/joe-blog/perlweeklychallenge-club - You should button to create **Pull Request**. + 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). +If you have any trouble with the above instructions then please get in touch with me anytime . -- cgit From 660b42cc0eded4160ef6e389730c8d93243f6c15 Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Thu, 2 Jan 2020 09:12:17 +0000 Subject: Updated README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 4ac010f359..febe0037c2 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Perl Weekly Challenge Club -This is the central repository for the members of **Perl Weekly Challenge**. The members can submit the solution to the challenge each week under version control. +This is the central repository for the members of [**Perl Weekly Challenge**](https://perlweeklychallenge.org). The members can submit the solution to the challenge each week under version control. ## How to contribute? Just submit Pull Request with your solutions. -- cgit From 3b43d9f0b6615bfe7ae9cf6581b779f2ae43f80d Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Sun, 5 Jan 2020 02:30:48 +0000 Subject: - Updated README with regard to renaming Raku. --- README.md | 74 +++++++++++++++++++++++++++++++-------------------------------- 1 file changed, 37 insertions(+), 37 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index febe0037c2..130ab0a79e 100644 --- a/README.md +++ b/README.md @@ -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 . -- cgit From e165799835e104cd8a28537371b4abe44df8f0c6 Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Sun, 5 Jan 2020 02:33:33 +0000 Subject: Minor update README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 130ab0a79e..5c7bc148aa 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ 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. **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? +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. -- cgit From fe605e08c124df72a5c90e37c2f661e3f65eef7c Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Fri, 28 Feb 2020 11:11:40 +0000 Subject: Added EZPWC link. --- README.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index 5c7bc148aa..6f7cd72c1f 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,10 @@ This is the central repository for the members of [**Perl Weekly Challenge**](https://perlweeklychallenge.org). The members can submit the solution to the challenge each week under version control. +## EZPWC - Easy Perl Weekly Challenges Script + +**Saif Ahmed**, respected member of **Team PWC**, created the tool **[EZPWC](https://github.com/saiftynet/EZPWC)** to help you with contributing to the weekly challenge. We highly recommend you to give it a try. If you have any questions/suggestions, then please raise an issue against the tool. + ## How to contribute? Just submit Pull Request with your solutions. -- cgit From 0f87f9a50b166b2bfbf97e766382d26dc7b6b55c Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Mon, 9 Mar 2020 11:26:58 +0000 Subject: Minor tweak, --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 6f7cd72c1f..022e777154 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Perl Weekly Challenge Club -This is the central repository for the members of [**Perl Weekly Challenge**](https://perlweeklychallenge.org). The members can submit the solution to the challenge each week under version control. +This is the central repository for the members of [**Perl Weekly Challenge**](https://perlweeklychallenge.org). The members can submit the solution to the challenge each week in their favourite programming languages, although the preferred languages are **Perl** and **Raku**. ## EZPWC - Easy Perl Weekly Challenges Script -- cgit From 04b4bd764ba8a06d20442d705ad6d8ab66486502 Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Fri, 3 Apr 2020 10:10:09 +0100 Subject: Minor tweak to README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 022e777154..2b7fcb607d 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ 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. **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? +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. @@ -46,9 +46,9 @@ Let us assume you want to submit solutions for **Challenge 002** and your Github 14. You should see a button to submit **Pull Request**. -## How to add new solution when you already have a fork? +## How to add new solution when you already have the forked branch? -Let us assume you already have a fork. If this is the first time you are using the same fork for submitting subsequent challenges solution. I also assume your GitHub user name is **joe-blog**. +Let us assume you already have the branch forked. If this is the first time you are using the same forked branch for submitting subsequent challenges solution. I also assume your GitHub user name is **joe-blog**. 1. Checkout out the **master** branch first. ``` -- cgit From 867311039700b6e03d0fa96f6d660dafcfe18bea Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Fri, 3 Apr 2020 10:37:32 +0100 Subject: Few more tweaks to README. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 2b7fcb607d..5979ca0764 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ 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. **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. +In case you have created a blog about your solutions, then create a file called **blog.txt** and add the link to it. In case you have more than one blog then create another file called **blog1.txt** and add your link there. ## Step-by-step instructions Let us assume you want to submit solutions for **Challenge 002** and your Github user name is **joe-blog**. @@ -46,9 +46,9 @@ Let us assume you want to submit solutions for **Challenge 002** and your Github 14. You should see a button to submit **Pull Request**. -## How to add new solution when you already have the forked branch? +## How to add new solution when you already have the forked repository? -Let us assume you already have the branch forked. If this is the first time you are using the same forked branch for submitting subsequent challenges solution. I also assume your GitHub user name is **joe-blog**. +Let us assume you already have the repository forked. If this is the first time you are using the same forked repository for submitting subsequent challenges solution. I also assume your GitHub user name is **joe-blog**. 1. Checkout out the **master** branch first. ``` -- cgit From b2871b84524563f388c234ea8f126950a1465a2d Mon Sep 17 00:00:00 2001 From: Mohammad S Anwar Date: Sun, 9 Aug 2020 09:49:33 +0100 Subject: Cosmetic changes to README. --- README.md | 42 +++++++++++++++++++++++++++++++++--------- 1 file changed, 33 insertions(+), 9 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 5979ca0764..1f43fd4ff4 100644 --- a/README.md +++ b/README.md @@ -16,17 +16,32 @@ In case you have created a blog about your solutions, then create a file called ## Step-by-step instructions 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**. +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**. +2. Go to your favourite terminal and **clone** your repository. + ``` + $ git clone https://github.com/joe-blog/perlweeklychallenge-club + ``` -3. Create a new branch for the solution **git checkout -b new-branch**. +3. Create a new branch for the solution + ``` + $ git checkout -b new-branch + ``` -3. Go to the **Challenge 002** folder **cd perlweeklychallenge-club/challenge-002**. +3. Go to the **Challenge 002** folder. + ``` + $ cd perlweeklychallenge-club/challenge-002 + ``` -4. If you find a folder with your name in the current folder then skip to next step otherwise create a new folder **mkdir joe-blog**. +4. If you find a folder with your name in the current folder then skip to next step otherwise create a new folder. + ``` + $ mkdir joe-blog + ``` -5. Change into your named folder **cd joe-blog**. +5. Change into your named folder. + ``` + $ cd joe-blog + ``` 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. @@ -36,11 +51,20 @@ Let us assume you want to submit solutions for **Challenge 002** and your Github 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**. -10. Once you are happy with your solutions, you should **add** it to the repository. First go back to **root** of the repository and then fire the command **git add challenge-002/joe-blog**. +10. Once you are happy with your solutions, you should **add** it to the repository. First go back to **root** of the repository and then fire the command + ``` + $ git add challenge-002/joe-blog + ``` -11. Commit your changes **git commit** +11. Commit your changes. + ``` + $ git commit + ``` -12. Push your changes **git push -u origin new-branch** +12. Push your changes. + ``` + $ git push -u origin new-branch + ``` 13. Now go to your fork repository in GitHub web portal **https://github.com/joe-blog/perlweeklychallenge-club** -- cgit