<?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: Nuno "Omega Leo" Diogo</title>
    <description>The latest articles on DEV Community by Nuno "Omega Leo" Diogo (@omegaleo).</description>
    <link>https://dev.to/omegaleo</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%2F14691%2Fcbe38574-db53-4ae7-b901-a7d16bd71291.jpg</url>
      <title>DEV Community: Nuno "Omega Leo" Diogo</title>
      <link>https://dev.to/omegaleo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/omegaleo"/>
    <language>en</language>
    <item>
      <title>UnityFlow - Automated Workflow for Unity Projects</title>
      <dc:creator>Nuno "Omega Leo" Diogo</dc:creator>
      <pubDate>Sat, 20 May 2023 11:55:43 +0000</pubDate>
      <link>https://dev.to/omegaleo/unityflow-automated-workflow-for-unity-projects-l5g</link>
      <guid>https://dev.to/omegaleo/unityflow-automated-workflow-for-unity-projects-l5g</guid>
      <description>&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;A repository with code and actions that can be useful for C# projects and also Unity projects.&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;maintainer must-haves&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  App Link
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/omegaleo/UnityFlow"&gt;https://github.com/omegaleo/UnityFlow&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Screenshots
&lt;/h3&gt;

&lt;p&gt;N/A&lt;/p&gt;

&lt;h3&gt;
  
  
  Description
&lt;/h3&gt;

&lt;p&gt;My entry takes an approach to the category of &lt;strong&gt;maintainer must-haves&lt;/strong&gt; where my goal is to do a set of tools/template repo to help devs deploy and keep their documentation and changelogs up-to-date, it'll mostly be for C# developers and consists of the following:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;auto-tag: C# project that will be called whenever an issue is created/updated and will properly tag the issue depending on what is written in the title/description. Example: If I write @feature in the description, once the workflow is called it'll tag that issue with the feature tag. &lt;/li&gt;
&lt;li&gt;changelog-generator: C# project that will be in charge of updating the changelog.md and also changes for the release whenever one is generated. Say for example, if I made a release with the tag v1.0.0, it'll call the workflow, get me all the commit messages since the last release that match a filter, update the release's description with those commit messages and also add the lines for it in the changelog.md&lt;/li&gt;
&lt;li&gt;documentation-helper: C# Project that will handle the automatic generation of documentation and is divided into 2 components:

&lt;ul&gt;
&lt;li&gt;Library: For now only has the DocumentationAttribute(used to mark methods/properties/classes for documentation, see image below for example) and DocumentationHelper, a static class that will go through all assemblies in the project and check for the DocumentationAttribute and return in a DocumentationStructure list that will be used to show the documentation;&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--Wnkj5Mwx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fzh4gq7zi2z7x37zqejs.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Wnkj5Mwx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fzh4gq7zi2z7x37zqejs.png" alt="Documentarion" width="800" height="119"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;DocumentationGenerator: Simple script that will be called manually from the Actions menu and that will update the documentation.md using the DocumentationHelper described above.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Link to Source Code
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/omegaleo/UnityFlow"&gt;https://github.com/omegaleo/UnityFlow&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Permissive License
&lt;/h3&gt;

&lt;p&gt;MIT&lt;/p&gt;

&lt;h2&gt;
  
  
  Background (What made you decide to build this particular app? What inspired you?)
&lt;/h2&gt;

&lt;p&gt;Well, as a Unity Dev for the last 5 years I've always wondered what sort of tools would help me greatly improve my workflow and so with that in mind I started developing this repo.&lt;/p&gt;

&lt;h3&gt;
  
  
  How I built it (How did you utilize GitHub Actions or GitHub Codespaces? Did you learn something new along the way? Pick up a new skill?)
&lt;/h3&gt;

&lt;p&gt;I have actions set up for the following:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When a new issue/pull request is created: Call the auto-tag project and tag the issue/pull request&lt;/li&gt;
&lt;li&gt;When a new release is created: Call the changelog-generator project and write a list of changes compared to the previous release based on commit descriptions&lt;/li&gt;
&lt;li&gt;Manually: Call the documentation-helper project to write documentation for the projects that have the library added to.&lt;/li&gt;
&lt;/ul&gt;

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

&lt;p&gt;N/A&lt;/p&gt;

</description>
      <category>githubhack23</category>
      <category>csharp</category>
    </item>
    <item>
      <title>My first time participating in a hackathon</title>
      <dc:creator>Nuno "Omega Leo" Diogo</dc:creator>
      <pubDate>Sat, 29 Apr 2023 20:14:11 +0000</pubDate>
      <link>https://dev.to/omegaleo/my-first-time-at-a-hackathon-2fgg</link>
      <guid>https://dev.to/omegaleo/my-first-time-at-a-hackathon-2fgg</guid>
      <description>&lt;p&gt;Hello everyone, although being a really old member of this platform I guess this is my first time ever doing a post 😅, so I don't know well where to start but the gist of it is that I decided to participate in the #GitHubHack23.&lt;br&gt;
My entry will take an approach to the category of &lt;strong&gt;maintainer must-haves&lt;/strong&gt; where my goal will be to do a set of tools/template repo to help devs deploy and keep their documentation and changelogs up-to-date, it'll mostly be for C# developers as I sadly don't have much experience with other languages and for now I have it divided into the following(still at a really WIP phase):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;auto-tag: C# project that will be called whenever an issue is created/updated and will properly tag the issue depending on what is written in the title/description. Example: If I write @feature in the description, once the workflow is called it'll tag that issue with the feature tag. &lt;/li&gt;
&lt;li&gt;changelog-generator: C# project that will be in charge of updating the changelog.md and also changes for the release whenever one is generated. Say for example, if I made a release with the tag v1.0.0, it'll call the workflow, get me all the commit messages since the last release that match a filter, update the release's description with those commit messages and also add the lines for it in the changelog.md&lt;/li&gt;
&lt;li&gt;documentation-helper: C# Project that will handle the automatic generation of documentation and is divided into 2 components:

&lt;ul&gt;
&lt;li&gt;Library: For now only has the DocumentationAttribute(used to mark methods/properties/classes for documentation, see image below for example) and DocumentationHelper, a static class that will go through all assemblies in the project and check for the DocumentationAttribute and return in a DocumentationStructure list that will be used to show the documentation;&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--Wnkj5Mwx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fzh4gq7zi2z7x37zqejs.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Wnkj5Mwx--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fzh4gq7zi2z7x37zqejs.png" alt="Documentarion" width="800" height="119"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;DocumentationGenerator: Simple script that will be called manually from the Actions menu and that will update the documentation.md using the DocumentationHelper described above.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm hoping to get this a bit more organized and also implement some helpful tools for Unity that will tie in to these projects.&lt;/p&gt;

&lt;p&gt;If you want to check out the current state of the project, it's currently public on &lt;a href="https://github.com/omegaleo/UnityFlow"&gt;Github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;All feedback is greatly appreciated :)&lt;/p&gt;

</description>
      <category>githubhack23</category>
      <category>csharp</category>
      <category>githubactions</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
