@matthewross07 this PR is a follow-on to the last one; the previous PR had the relevant code to do the WQP pull, while this one contains a large number of small files representing the status of the WQP pull. I separated them because I didn't want these indicator/status files to overwhelm the code files, which might have rendered the previous PR unreadable.
Would be great to talk with you on the phone after you've merged this PR and updated your installation of scipiper, to see if we can get the build flowing properly on your computer. First real-world test of new scipiper features!
Specifics of this PR
Committing many small files related to the pull of raw WQP data:
files ending in .ind, which each serve as a promise that a data file was created and possibly posted to google drive
files in build/status ending in .yml, which contain the information required for scipiper/remake to determine whether a promise is up to date
Also updating .gitignore to avoid committing .RData and .feather files to the repo
@matthewross07 this PR is a follow-on to the last one; the previous PR had the relevant code to do the WQP pull, while this one contains a large number of small files representing the status of the WQP pull. I separated them because I didn't want these indicator/status files to overwhelm the code files, which might have rendered the previous PR unreadable.
Would be great to talk with you on the phone after you've merged this PR and updated your installation of
scipiper, to see if we can get the build flowing properly on your computer. First real-world test of newscipiperfeatures!Specifics of this PR
Committing many small files related to the pull of raw WQP data:
.ind, which each serve as a promise that a data file was created and possibly posted to google drive.yml, which contain the information required forscipiper/remaketo determine whether a promise is up to dateAlso updating .gitignore to avoid committing .RData and .feather files to the repo