>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3572032. --> Reported by: [jurgenhaas](https://www.drupal.org/user/168924) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We should remove the built bundle from the repository, as this will just cause merge conflicts and confusion. Let's take the same approach that @justafish has taken in the conductor module. There is a release task in the pipeline which builds and commits the bundle into the tagged branch and commits/pushes that.</p> <p>Here is the pipeline to get this from: <a href="https://git.drupalcode.org/project/conductor/-/blob/2.x/.gitlab-ci.yml?ref_type=heads">https://git.drupalcode.org/project/conductor/-/blob/2.x/.gitlab-ci.yml?ref_type=heads</a></p> <p>But that requires us to tag a release soon; otherwise regular users won't be able to easily test this.</p> <p>For developers, we need to make clear that they have to run <code>npm run build</code> when they're working with untagged branches.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>