Revision abb645178e2f3e5ac4865ed461ff092db9118728 authored by Bryna Hazelton on 14 March 2023, 22:19:09 UTC, committed by Bryna Hazelton on 15 March 2023, 18:14:56 UTC
github.ref is the correct thing to use here, see: https://docs.github.com/en/actions/learn-github-actions/contexts#github-context I guess that the github.event.ref gave the same value when the triggering event is a push but not when the triggering event is a release.
1 parent bb2217c
File | Mode | Size |
---|---|---|
src | ||
tests | ||
__init__.py | -rw-r--r-- | 191 bytes |
aipy_extracts.py | -rw-r--r-- | 20.8 KB |
corr_fits.pyx | -rw-r--r-- | 13.0 KB |
fhd.py | -rw-r--r-- | 28.8 KB |
mir.py | -rw-r--r-- | 29.1 KB |
mir_meta_data.py | -rw-r--r-- | 130.2 KB |
mir_parser.py | -rw-r--r-- | 156.0 KB |
miriad.py | -rw-r--r-- | 97.0 KB |
ms.py | -rw-r--r-- | 98.9 KB |
mwa_corr_fits.py | -rw-r--r-- | 77.4 KB |
uvdata.py | -rw-r--r-- | 629.5 KB |
uvfits.py | -rw-r--r-- | 69.9 KB |
uvh5.py | -rw-r--r-- | 81.2 KB |
Computing file changes ...