We decided today that having the two mx-bluesky and hyperion repos is causing us too much dependency overhead. Hyperion should be merged into here.
Things that must happen when they are merged:
Git history of hyperion is preserved
All hyperion tests are still run and pass
Issues on hyperion repo are moved to mx-bluesky (with an appropriate label)
Things that should happen (e.g. make a new issue for them if hard):
The structure of mx-bluesky needs to be well documented
All the GH actions that move things on the Hyperion project board still work (with the caveat that they only work on things tagged with the hyperion label)
Slack messages on releases still get pushed to the hyperion channel
Things we would then like to add:
Release notes are now going to be a bit messy, it would be nice to have an automated way of adding a hyperion heading to them
We decided today that having the two
mx-bluesky
andhyperion
repos is causing us too much dependency overhead. Hyperion should be merged into here.Things that must happen when they are merged:
Things that should happen (e.g. make a new issue for them if hard):
mx-bluesky
needs to be well documentedhyperion
channelThings we would then like to add:
hyperion
heading to themNice to haves: