<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Github on Hi, I&#39;m Muhammad Amal</title>
    <link>https://muhammadamal.my.id/tags/github/</link>
    <description>Recent content in Github on Hi, I&#39;m Muhammad Amal</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 May 2023 09:00:00 +0700</lastBuildDate>
    <atom:link href="https://muhammadamal.my.id/tags/github/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Two-Way Sync Between Jira and GitHub Issues Without Losing Your Mind</title>
      <link>https://muhammadamal.my.id/blog/jira-github-issues-two-way-sync/</link>
      <pubDate>Thu, 18 May 2023 09:00:00 +0700</pubDate>
      <guid>https://muhammadamal.my.id/blog/jira-github-issues-two-way-sync/</guid>
      <description>Designing a two-way Jira &amp;lt;-&amp;gt; GitHub Issues sync that survives webhook loops, conflicting edits, and field-mapping mismatches. The patterns that actually work in production.</description>
    </item>
    <item>
      <title>Auto-Assigning Jira Tickets from GitHub PR Events with n8n</title>
      <link>https://muhammadamal.my.id/blog/jira-auto-assignment-github-events/</link>
      <pubDate>Wed, 11 May 2022 09:00:00 +0700</pubDate>
      <guid>https://muhammadamal.my.id/blog/jira-auto-assignment-github-events/</guid>
      <description>n8n workflow: GitHub PR events → auto-assign + transition Jira tickets. Webhook → parser → Jira API.</description>
    </item>
  </channel>
</rss>
