-
Notifications
You must be signed in to change notification settings - Fork 0
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
Tweaks to workflow and improvements to docs #112
Conversation
Looks fine to me to throw more of the content in that one directory, while being smart about having different heartbeat files. |
Yes. Also note that the heart attack files are not changed, so the default one would kill both. |
What is status on this one? |
I still have a couple commits to make |
… notify/alert aca, custom notification.
The column description updates seem a good idea and seem benign. Was that tested in the "run on /proj/sot/ska/jgonzalez/miniconda3/envs/agasc before the last four commits (disposition comments, test fix, table column docs)" test item? Meaning, was a file updated that had the new descriptions and then the tests still pass? |
that was tested on my mac. I ran an update and checked that the resulting file had the descriptions in it, but I did not run on HEAD. |
Right. I'm not sure about test coverage, but I was thinking that the agasc.test() tests should run in an area that can see the updated-with-descriptions file . |
the column descriptions are only in the fits file, and not in the supplement file, so I don't see how it can affect agasc.test |
OK. Sounds good. Seems like at some point we might need a test that reads the fits files if that isn't in coverage? But sounds good for being done to approve this PR. |
Description
Testing
/proj/sot/ska/jgonzalez/miniconda3/envs/agasc
before the last four commits (disposition comments, test fix, table column docs)