auto sync & publish upstream release #2
Conversation
every 3 days, this gh actions script will look at the upstream repository (topQuadrant SHACL) and ingest its changes if there are any. If a new release has been done, it will also copy that and make a new release with the same version number.
|
hold up, this is not right. It's using the wrong repository now, will change it now. |
using topquadrant repo instead of ordes one as head
|
Should be right now. @cmdoret Is there any way to test if this works without actually pulling the changes to master? |
|
Perhaps temporarily changing the base branch here whould work? |
|
Hmmm, this is kind of what I had done with the upstream and downstream branches, so in that sense it should work. I was hoping there was an ability to make a sort of pull request based on the run of GitHub Actions - a human check on what the actions are proposing to do, but I think this is just the opposite of what GHA is made for. I think we can just see what happens in 3 days. Probably a release will be made (since the latest version on SDSC-ORD/SHACL is called "test". It's unlikely that Holger will release a new version of shacl in the coming 3 days anyway (weekend). If @supermaxiste also still wants to review to see what our "issue speedrun" has resulted in I let you do the honors of merging if you are satisfied. We can then close the ticket and if anything needs to be changed/improved, we can make a new ticket. |
|
Besides my minor comments, all the rest looks good and really excited to see the first SDSC-ORD container of a relatively popular tool 🤩 great job @rmfranken! |
every 3 days, this gh actions script will look at the upstream repository (topQuadrant SHACL) and ingest its changes if there are any. If a new release has been done, it will also copy that and make a new release with the same version number.