Overview
We should implement the ability to run the add-data GHA on an existing branch. If selected, it should use this branch when creating the pipeline files - particularly when assigning lookups (and therefore entity-organisations). It should also attach the updates to any pre-existing Pull Request that exists on that branch.
This will mean that users adding data can add multiple endpoints (from either the same or different collections/datasets) to the same PR, which will reduce the number of PRs and reviews necessary to get onto the platform. It will also reduce the number of merge conflicts encountered.
Detailed Approach
After the Check, when assigning the lookups, check if there is already an open branch(es) with an open PR (i.e. not closed/merged) that was created by the Add Data process. If not, carry on as usual and create a new branch. If so, ask the user if they would like to add to this existing branch. If there are multiple open branches, allow the user to select the branch they wish to add to. The Github Action should then run on this branch so that any look-ups that have already been created in the branch are taken into account (so therefore the new lookups would be after those ones).
Also, within this ticket, we can improve the naming of the PR raised by the bot.
Overview
We should implement the ability to run the add-data GHA on an existing branch. If selected, it should use this branch when creating the pipeline files - particularly when assigning lookups (and therefore entity-organisations). It should also attach the updates to any pre-existing Pull Request that exists on that branch.
This will mean that users adding data can add multiple endpoints (from either the same or different collections/datasets) to the same PR, which will reduce the number of PRs and reviews necessary to get onto the platform. It will also reduce the number of merge conflicts encountered.
Detailed Approach
After the Check, when assigning the lookups, check if there is already an open branch(es) with an open PR (i.e. not closed/merged) that was created by the Add Data process. If not, carry on as usual and create a new branch. If so, ask the user if they would like to add to this existing branch. If there are multiple open branches, allow the user to select the branch they wish to add to. The Github Action should then run on this branch so that any look-ups that have already been created in the branch are taken into account (so therefore the new lookups would be after those ones).
Also, within this ticket, we can improve the naming of the PR raised by the bot.