Create and use de-identified research databases. Preprocess, extract text, anonymise/de-identify, link, apply natural language processing, query for research, manage consent for contact.
GNU General Public License v3.0
19
stars
7
forks
source link
Remove hardcoded GitHub release in installer.sh #78
The installer.yml GitHub action is triggered when practically any source file in the repo changes. This should be updated to install from local checkout rather than fetching the installer.sh standalone script from the latest release. Otherwise it won't test with the files that were recently pushed.
The release.yml GitHub action is triggered when a new tag is pushed to the repository. This should be updated to create our own tar file asset that can be accessed as "latest" and test the installer with the installer.sh fetched from the latest release.
I've had to hardcode the latest GitHub release version in the installer script because the tarball that GItHub creates automatically for a new release can't be accessed from https://github.com/RudolfCardinal/crate/releases/latest/download/crate.tar.gz like manually uploaded assets can.
The
installer.ymlGitHub action is triggered when practically any source file in the repo changes. This should be updated to install from local checkout rather than fetching theinstaller.shstandalone script from the latest release. Otherwise it won't test with the files that were recently pushed.The
release.ymlGitHub action is triggered when a new tag is pushed to the repository. This should be updated to create our own tar file asset that can be accessed as "latest" and test the installer with theinstaller.shfetched from the latest release.