-
Notifications
You must be signed in to change notification settings - Fork 0
Ticket 7914 - pull latest instrument scripts master #285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ticket 7914 - pull latest instrument scripts master #285
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please fix remaining ruff error (which is just imports in wrong order, and can be auto-fixed).
- Can you add something to https://isiscomputinggroup.github.io/ibex_developers_manual/scripting/instrument-scripts.html about this setup, expected branches, what we decided the auto-update implementation should look like, etc. Or add it to https://github.com/ISISNeutronMuon/InstrumentScripts/wiki and link through to it much more clearly from our manual.
installation_and_upgrade/ibex_install_utils/tasks/server_tasks.py
Outdated
Show resolved
Hide resolved
|
||
@task("Set up shared instrument scripts library") | ||
@task("Merge master into local shared instrument scripts library") | ||
def update_shared_scripts_repository(self) -> None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need a clearer prompt to explicitly inform scientists that their InstrumentScripts
library has been updated. It is nominally maintained by scientists with oversight from us, but we do need to make sure they get told when it has been updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I was thinking to make it very explicit prompt to a developer that they need to tell a scientist they've done this. But maybe that's "obvious", any time we go and fiddle with instrument scripts.
See ticket for details