<?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: Hally</title>
    <description>The latest articles on DEV Community by Hally (@itshally).</description>
    <link>https://dev.to/itshally</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%2F277288%2F9ac148fe-0c06-497c-9763-0ccbc7ca2603.GIF</url>
      <title>DEV Community: Hally</title>
      <link>https://dev.to/itshally</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/itshally"/>
    <language>en</language>
    <item>
      <title>How to make your cloned Github repo as your Exercism workspace</title>
      <dc:creator>Hally</dc:creator>
      <pubDate>Mon, 15 Feb 2021 01:42:15 +0000</pubDate>
      <link>https://dev.to/itshally/how-to-make-your-cloned-github-repo-as-your-exercism-s-workspace-2jdf</link>
      <guid>https://dev.to/itshally/how-to-make-your-cloned-github-repo-as-your-exercism-s-workspace-2jdf</guid>
      <description>&lt;p&gt;Some people will say that you don't need to do it because your Exercism solutions are already posted on your Exercism profile. However, some still want to push it to their Github repo and I am among them. &lt;/p&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%2Fi%2F8gft8b797b3eq7j9aebo.gif" 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%2Fi%2F8gft8b797b3eq7j9aebo.gif" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Note:
&lt;/h3&gt;

&lt;p&gt;These steps can be applied as well if you just want to simply rename, move, or just going to change your Exercism workspace. In other words, if you just want to configure your Exercism workspace then you just only need to follow &lt;strong&gt;Step 3 &amp;amp; Step 4&lt;/strong&gt;. But in this case, we will stick to the topic. Shall we?&lt;/p&gt;

&lt;h2&gt;
  
  
  Here are the steps:
&lt;/h2&gt;

&lt;h4&gt;
  
  
  Step 1
&lt;/h4&gt;

&lt;p&gt;Create a new Github repository for your Exercism solutions if you haven't created one yet. &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%2Fi%2Fl6gvkipjj0kfxp8dteoy.JPG" 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%2Fi%2Fl6gvkipjj0kfxp8dteoy.JPG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Step 2
&lt;/h4&gt;

&lt;p&gt;Once you're done, clone your Github repo to your machine.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git clone https://github.com/&amp;lt;your-username&amp;gt;/&amp;lt;your-repo-name&amp;gt;.git
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Done cloning? Alright, let's go to the 3rd step! &lt;/p&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%2Fi%2Fnyjqovdr74o30fao1jsy.gif" 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%2Fi%2Fnyjqovdr74o30fao1jsy.gif" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Step 3
&lt;/h4&gt;

&lt;p&gt;This time, we are going to configure our Exercism and this is the most important part. &lt;/p&gt;

&lt;p&gt;Using your &lt;strong&gt;&lt;em&gt;Command Prompt&lt;/em&gt;&lt;/strong&gt;, go to the root directory where your Exercism CLI is located. Mine is in the..&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;C:\Users\hally&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  Step 4
&lt;/h4&gt;

&lt;p&gt;Okay patience. Now, to configure your Exercism workspace, you need to run this command line&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;exercism configure -w=&amp;lt;type-your-new-location-with-your-repo-name&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;-w&lt;/code&gt; is short for &lt;code&gt;--workspace&lt;/code&gt;.&lt;br&gt;
In my situation, I have to move it to another drive.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;exercism configure -w="G:/Programming Projects/Github/&amp;lt;cloned-repo-name&amp;gt;"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  Step 5
&lt;/h4&gt;

&lt;p&gt;Make sure that you'll see this line on your command prompt:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;You have configured the Exercism command-line client:
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And make sure that on the &lt;strong&gt;&lt;em&gt;Workspace&lt;/em&gt;&lt;/strong&gt; line displays your new directory. &lt;/p&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%2Fi%2Fx1za09igxz0gzg3wo0ii.JPG" 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%2Fi%2Fx1za09igxz0gzg3wo0ii.JPG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If so, you can now start downloading the exercises and it should be downloaded straight to your cloned repository.&lt;/p&gt;

&lt;p&gt;Try to check your Git status:&lt;br&gt;
&lt;/p&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;But after you solved your downloaded challenge and then want to push it now, you can do so.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git add . 
git commit -m “adding a solution”
git push
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&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%2Fi%2Fgunfjt8lz0zexi9bw07a.gif" 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%2Fi%2Fgunfjt8lz0zexi9bw07a.gif" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Source
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://medium.com/@JimLynchCodes_76316/how-to-setup-exercism-cli-to-use-your-own-github-repository-5892d401b39f" rel="noopener noreferrer"&gt;How To Setup Exercism CLI To Use Your Own Github Repository by Jim Lynch&lt;/a&gt;&lt;/p&gt;

</description>
      <category>exercism</category>
      <category>webdev</category>
      <category>github</category>
    </item>
    <item>
      <title>Issue Notifier</title>
      <dc:creator>Hally</dc:creator>
      <pubDate>Thu, 17 Sep 2020 15:54:53 +0000</pubDate>
      <link>https://dev.to/itshally/issue-notifier-2c2b</link>
      <guid>https://dev.to/itshally/issue-notifier-2c2b</guid>
      <description>&lt;h3&gt;
  
  
  Our Workflow
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--B6qdN_a4--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/8xntkgptfp15wd3rujyi.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--B6qdN_a4--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/8xntkgptfp15wd3rujyi.png" alt="icon used" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Creating an &lt;strong&gt;Issue Notifier&lt;/strong&gt; is our first entry for the Github Actions Hackathon. It notifies the owner of the repository on Slack when someone submits/&lt;strong&gt;opens&lt;/strong&gt; an issue. In addition, this project can help the maintainers to track issues that other contributors submitted. Thus, this creates more interaction for an open-source projects.&lt;/p&gt;

&lt;p&gt;When using this project, make sure that you have your Incoming Webhook URL. &lt;/p&gt;

&lt;p&gt;It is a nice experience to create an app for your Development Slack Workspace. You can go to this &lt;a href="https://api.slack.com/apps"&gt;link&lt;/a&gt; to start this. &lt;/p&gt;

&lt;p&gt;Start by giving your slack app a nice and flaring name and choose which workspace to use it for. Then after you created your first app, go to the Incoming Webhooks Tab:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--hSp9ouC6--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/v2elvk3wbx1fql0m4ya2.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--hSp9ouC6--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/v2elvk3wbx1fql0m4ya2.JPG" alt="incoming webhooks tab on slack" width="256" height="568"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Activate the Incoming Webhooks. Then at the bottom, click the &lt;strong&gt;Add New Webhook to Workspace&lt;/strong&gt; button and select which channel it will make the posts.&lt;/p&gt;

&lt;p&gt;Copy that link and paste it on your repository Secrets environment.&lt;/p&gt;

&lt;p&gt;Name that secret &lt;code&gt;SLACK_WEBHOOK_URL&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--d6Wd0yZV--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/erh2eg47t6iu5kkpbd3u.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--d6Wd0yZV--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/erh2eg47t6iu5kkpbd3u.JPG" alt="creating a secret environment variable" width="880" height="505"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is an example of what we created:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--6ujsiCJ7--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/uqcrwrbq0hy7iwybbnss.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--6ujsiCJ7--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/uqcrwrbq0hy7iwybbnss.png" alt="an example of the issue notifier post" width="880" height="369"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Submission Category:
&lt;/h3&gt;

&lt;p&gt;It could fall on &lt;strong&gt;&lt;em&gt;Maintainer Must-Haves&lt;/em&gt;&lt;/strong&gt;, but I guess it is good under &lt;strong&gt;&lt;em&gt;Wacky Wildcards&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Yaml File or Link to Code
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/itshally/issue-notifier/blob/master/.github/workflows/main.yml"&gt;Issue Notifier File&lt;/a&gt;&lt;br&gt;
&lt;/p&gt;
&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--566lAguM--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/itshally"&gt;
        itshally
      &lt;/a&gt; / &lt;a href="https://github.com/itshally/issue-notifier"&gt;
        issue-notifier
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      This is a submission for the Github Actions Hackathon on Dev.
    &lt;/h3&gt;
  &lt;/div&gt;
  &lt;div class="ltag-github-body"&gt;
    
&lt;div id="readme" class="md"&gt;
&lt;h1&gt;
Issue Notifier&lt;/h1&gt;
&lt;p&gt;Hello All
So in this #githubactionhackathon we are submitting  &lt;strong&gt;Issue Notifier&lt;/strong&gt;
Creating your own Issue Notifier is our first entry for the Github Actions Hackathon. It notifies the owner of the repository on Slack when someone submits/opens an issue. In addition, this project can help the maintainers to track issues that other contributors submitted. Thus, this creates more interaction for an open-source projects.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Prequisities for running this project&lt;/li&gt;
&lt;li&gt;Must have Incoming Webhook URL by using this link &lt;a href="https://api.slack.com/apps" rel="nofollow"&gt;Slackapps&lt;/a&gt; you can create your app and then Activate the Incoming Webhooks. Then at the bottom, click the Add New Webhook to Workspace button and select which channel it will make the posts
&lt;a rel="noopener noreferrer" href="https://camo.githubusercontent.com/88b66c6cc3c00fbbd17d8292cfcecdb9772f51b25b024e96243d49cd13b9c897/68747470733a2f2f6465762d746f2d75706c6f6164732e73332e616d617a6f6e6177732e636f6d2f692f68343134786f71776434366676697138733772702e4a5047"&gt;&lt;img src="https://camo.githubusercontent.com/88b66c6cc3c00fbbd17d8292cfcecdb9772f51b25b024e96243d49cd13b9c897/68747470733a2f2f6465762d746f2d75706c6f6164732e73332e616d617a6f6e6177732e636f6d2f692f68343134786f71776434366676697138733772702e4a5047" alt="Alt Text"&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Here is an examples of what we created and you can see what we are geeting in our slack channel
&lt;a rel="noopener noreferrer" href="https://camo.githubusercontent.com/d390dbbfc2e9488e710e9bd82f0f7235b6df07adc4f1c13d697aea1568b031b0/68747470733a2f2f6465762d746f2d75706c6f6164732e73332e616d617a6f6e6177732e636f6d2f692f6a6f643162386c6f7632396339346f37696474692e706e67"&gt;&lt;img src="https://camo.githubusercontent.com/d390dbbfc2e9488e710e9bd82f0f7235b6df07adc4f1c13d697aea1568b031b0/68747470733a2f2f6465762d746f2d75706c6f6164732e73332e616d617a6f6e6177732e636f6d2f692f6a6f643162386c6f7632396339346f37696474692e706e67" alt="Alt Text"&gt;&lt;/a&gt;
&lt;a rel="noopener noreferrer" href="https://camo.githubusercontent.com/e08153bfea3dda25e3d8cf9d37af1e34d7a926c7de413a11c79f98226ff282c4/68747470733a2f2f6465762d746f2d75706c6f6164732e73332e616d617a6f6e6177732e636f6d2f692f70387a7a71323931617336343872317965746c372e706e67"&gt;&lt;img src="https://camo.githubusercontent.com/e08153bfea3dda25e3d8cf9d37af1e34d7a926c7de413a11c79f98226ff282c4/68747470733a2f2f6465762d746f2d75706c6f6164732e73332e616d617a6f6e6177732e636f6d2f692f70387a7a71323931617336343872317965746c372e706e67" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;
Submission Category:&lt;/h1&gt;
&lt;p&gt;It could fall on Maintainer Must-Haves, but I guess it is good under Wacky Wildcards-hally&lt;/p&gt;
&lt;h1&gt;
Additional&lt;/h1&gt;…&lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="gh-btn-container"&gt;&lt;a class="gh-btn" href="https://github.com/itshally/issue-notifier"&gt;View on GitHub&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;


&lt;h3&gt;
  
  
  Additional Resources / Info
&lt;/h3&gt;

&lt;p&gt;Our project uses &lt;a href="https://github.com/marketplace/actions/slack-incoming-webhook"&gt;Slack Incoming Webhook&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Creators
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://dev.to/itshally"&gt;Hally&lt;/a&gt;&lt;br&gt;
&lt;a href="https://dev.to/krishnakakade"&gt;Krishna&lt;/a&gt;&lt;/p&gt;

</description>
      <category>actionshackathon</category>
      <category>github</category>
      <category>opensource</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
