<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Need better approach to solve wrong commits on Content Pack in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/need-better-approach-to-solve-wrong-commits-on-content-pack/m-p/1242396#M4200</link>
    <description>&lt;P&gt;Scenario:&amp;nbsp; Two developer working on same playbook on Dev environment. For ex&lt;/P&gt;
&lt;P&gt;Playbook Name: &lt;STRONG&gt;XXX_playbook&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Developer &lt;STRONG&gt;A&lt;/STRONG&gt; &amp;amp; Developer &lt;STRONG&gt;B&lt;/STRONG&gt; working on&amp;nbsp;&lt;STRONG&gt;XXX_playbook &lt;/STRONG&gt;and both make changes independently. 'A' makes first commit on develop branch. Then, 'B' makes second commit. B assumes his changes are ready to be promoted to prod. But, 'A' not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now, if the content pack is promoted to prod, then 'A' changes also goes to prod along with 'B' which SHOULDN'T be.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any solution to handle this scenario?&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Nov 2025 16:27:03 GMT</pubDate>
    <dc:creator>V.Kopparad</dc:creator>
    <dc:date>2025-11-21T16:27:03Z</dc:date>
    <item>
      <title>Need better approach to solve wrong commits on Content Pack</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/need-better-approach-to-solve-wrong-commits-on-content-pack/m-p/1242396#M4200</link>
      <description>&lt;P&gt;Scenario:&amp;nbsp; Two developer working on same playbook on Dev environment. For ex&lt;/P&gt;
&lt;P&gt;Playbook Name: &lt;STRONG&gt;XXX_playbook&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Developer &lt;STRONG&gt;A&lt;/STRONG&gt; &amp;amp; Developer &lt;STRONG&gt;B&lt;/STRONG&gt; working on&amp;nbsp;&lt;STRONG&gt;XXX_playbook &lt;/STRONG&gt;and both make changes independently. 'A' makes first commit on develop branch. Then, 'B' makes second commit. B assumes his changes are ready to be promoted to prod. But, 'A' not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now, if the content pack is promoted to prod, then 'A' changes also goes to prod along with 'B' which SHOULDN'T be.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any solution to handle this scenario?&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Cortex XSOAR" id="Cortex_XSOAR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Nov 2025 16:27:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/need-better-approach-to-solve-wrong-commits-on-content-pack/m-p/1242396#M4200</guid>
      <dc:creator>V.Kopparad</dc:creator>
      <dc:date>2025-11-21T16:27:03Z</dc:date>
    </item>
  </channel>
</rss>

