You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be extremely nice to be able to automate as much as possible the updating of the GHA workflows (I say this having just done this manually, in conjunction with VG).
A big obstacle to doing this is the organization of cbeleites/hyperSpec -- the package itself is inside a folder called hyperSpec. I propose that when cbeleites/hyperSpec is moved to r-hyperspec/hyperSpec that we make the folder structure like all the other repos by eliminating the outer folder. If we do this, then we can write a GHA/bash/R script that will deploy workflow updates to all repos when we trigger it. There are two files that are identical across all the repos except just slightly different in cbeleites/hyperSpec due to the different path. It would be nice to eliminate this special case.
The text was updated successfully, but these errors were encountered:
It would be extremely nice to be able to automate as much as possible the updating of the GHA workflows (I say this having just done this manually, in conjunction with VG).
A big obstacle to doing this is the organization of
cbeleites/hyperSpec
-- the package itself is inside a folder calledhyperSpec
. I propose that whencbeleites/hyperSpec
is moved tor-hyperspec/hyperSpec
that we make the folder structure like all the other repos by eliminating the outer folder. If we do this, then we can write a GHA/bash/R script that will deploy workflow updates to all repos when we trigger it. There are two files that are identical across all the repos except just slightly different incbeleites/hyperSpec
due to the different path. It would be nice to eliminate this special case.The text was updated successfully, but these errors were encountered: