Uploaded image for project: 'Ibexa IBX'
  1. Ibexa IBX
  2. IBX-4358

App development github integration

    XMLWordPrintable

Details

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • Ibexa Connect

    Description

      Setup processes using github workflows to synchronize a Connect App and a github repository.

      Branches and app mapping

      Each branch on github is mapped to a copy of the app on Connect:

      • main is mapped to the ibexa-dxp app on the shared account (productmanagement@ibexa.co)
      • custom branches created by developers are mapped to a copy of the app on the developer’s account, suffixed with the branch’s name (ibexa-dxp-:branch), and named after it as well

      Workflows

      • creating a branch creates a copy of the base branch on the branch’s creator’s Connect account
      • changes can be committed using a custom action (console command ? action on github ?)
      • the pull-request is created the usual way
        must add the shared URL to the app to the PR so that QA can install it for testing
      • when the pull-request is merged, the app copy overwrites the base app (need to handle conflicts / rebases ?)
      • when the branch is deleted, the matching copy is deleted

      Open questions

      • do we want to integrate tagging as well ? tagging the main branch approves and compiles the app.
      • how do we handle merge conflicts ? we need some rebase, but what is it triggered by ?
      • clarify how commits are handled

       

       

       

      Designs

        Attachments

          Activity

            People

              pawel.niedzielski@ibexa.co Paweł Niedzielski
              bertrand.dunogier@ibexa.co Bertrand Dunogier
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: