-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Description
As a user of the InstrumentScripts / Scans library, I would like my scripts repository to be brought up to date frequently. At the moment, we do this manually on a case-by-case basis as appropriate, we should put a more well defined process into place as discussed here: #7626 (comment).
In order to more easily deploy changes to the Instrument Scripts repo, we should have a utility script / deploy upgrade step that pulls the latest master from the remote and attempts to integrate those changes into the local folder on the instrument specific branch.
Acceptance Criteria
What is the acceptance criteria?
- There is an automated script that updates the scripts repository in /Instrument/Scripts/. This should:
- Pull latest master
- Attempt to merge master into instrument branch (
NDX<INST>) - If the merge fails, this should give the user options to skip or force overwrite
- For avoidance of doubt this is only during deploy, not a regular task
Discussed planning 10/07/2025 before recording started
Extra Information
- Depends on Instrument Scripts: Communicate plan to Scientists #7915
- The approach suggested in this ticket still requires going around each individual beamline and running the upgrade script on the NDX. If you have suggestions on how to circumvent this, please leave a comment!
How to Test
verbose instructions for reviewer to test changes
(Add before making a PR)
Metadata
Metadata
Assignees
Type
Projects
Status
Done