ISISComputingGroup / ISISComputingGroup/IBEX
GUI OPIs: Automate the gathering of OPIs into the server OPI repo
- Dominant language
- No language data
- Stars
- 6
- Forks
- 2
- Avg merge
- 16h 40m
- Merged PRs (30d)
- 2
Description
As someone developing OPIs for use in the IBEX client, I want to be able to get the OPIs from the server (see https://github.com/ISISComputingGroup/IBEX/issues/6562 for the discussion) and to get the ones that match the version of the IOC in use where appropriate.
## Acceptance Criteria
- [ ] The OPI for one IOC has been moved from the server OPI repo into the appropriate support module
- [ ] There is a method which on make of the IOC will copy that OPI into the server OPI repo for serving to the client
- [ ] The OPI is still available in the client
- [ ] Either the githooks for OPIs are applied to the appropriate support module or a different method of ensuring that behaviour is defined and enacted (this ticket is being created before that decision should be made)
- [ ] A tech debt/umbrella ticket with a list of OPIs that can be moved into support modules is created, listing at least 10 more OPIs to be considered and the total of OPIs currently in the folder
- [ ] The workflow is updated so that new OPIs are created in the appropriate support module
## Notes
- The creation of the ticket with the number of OPIs is so that we can consider them in a chunks, if we know there are 100 OPIs to consider, then rather than list all 100 only the first ten are listed, but that would be 10 out of 100, there would still be an indication that there are 90 more to look at.
- OPIs that do not associate to a submodule should remain in the server OPI repo
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.