-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add github actions to ska packages #295
Comments
@jeanconn, would you mind merging the PRs for a couple of packages you intend to release today? (if any). Quaternion, for example. After you agree, that is. |
Per our conversation, none of these are going today, but Quaternion will probably go next week if we want to start with that as a dog fooding test case. |
@javierggt yes, that'd be great |
there is also an action that edits the release notes to mention all merges since last release. That one works in test repositories, but I do not know if it works fine everywhere. |
Since we can still edit the release notes, I think it is benign if it isn't perfect yet. |
@jzuhone I can't push a branch to the repositories. |
They generally do PRs from their own forks which I think you could do too in this case @javierggt ? |
@javierggt which repo did you try? |
@javierggt try now. |
I just noticed that sot/find_attitude is not included here. It should be, shouldn't it? |
Yes. I'm not sure about the best way to check for any other missing ones but assume we'll notice if we just have missing automatic builds for a dependency. |
I noticed by creating a ska3-dev environment including this channel: https://cxc.cfa.harvard.edu/mta/ASPECT/ska3-conda/dev The only ska3-dev package not coming from this channel was find_attitude (and the acisops packages). |
As the title says: we will be adding automated actions to ska packages, and this is the uber-issue.
Changes should include:
I will first add Chandra.Time for you to check. Then I will add the rest. The list of packages is:
NOTE the ones missing in the list above
ACIS ops:
The text was updated successfully, but these errors were encountered: