Skip to content
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

Merge Hyperion into this repo #169

Closed
DominicOram opened this issue Aug 21, 2024 · 1 comment · Fixed by #172
Closed

Merge Hyperion into this repo #169

DominicOram opened this issue Aug 21, 2024 · 1 comment · Fixed by #172

Comments

@DominicOram
Copy link
Contributor

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

Nice to haves:

@DominicOram
Copy link
Contributor Author

Proposed folder structure:

mx_bluesky
 - common
 - beamlines
    - i04
       - thawing.py
    - i24
       - ssx
 - hyperion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant