Run as github action?

Hi @kimrutherford

With the new svn repo that I can access without authentication the update of the file can be ran as a github action (the only one in the repo), don't know if that is useful. In principle it should commit the changes but I have to wait for the next change in the repo to test whether it actually does.

Hi @manulera

If it's not a lot of work, I think that automating with GitHub Actions is a good idea.

It was already done, I am just not sure whether the output will be committed to the repo (I think so but I have to wait until next change in the genome)

Hi @kimrutherford the github action works, and made this last commit.

0cdc284

Hi @kimrutherford, as you said the action can be easily triggered using github CLI. I have added a file with the command to do so. It's a one-liner but good to keep it there in case syntax changes.

https://github.com/pombase/genome_changelog/blob/master/trigger_action.sh

I re-open the issue, you can close once this is added to the overnight run.

https://github.com/pombase/genome_changelog/blob/master/trigger_action.sh

Run this weekly, initially.

Investigate running using the pombase GitHub organisation.

Hi @manulera

After having a look at the documentation it looks like we could change the Actions config from:

genome_changelog/.github/workflows/update.yml

Lines 2 to 5 in 9d5cbdd

    
           on: 
        
             workflow_dispatch: 
        
             repository_dispatch: 
        
               types: [trigger_update]

to:

on:
  schedule:
     - cron: '30 2 * * 0,3'

Does that seem OK to you? If so, I'll try it.

"0,3" means Sunday and Wednesday (hopefully).

I wonder if we can allow for the schedule and for the trigger at the same time with something like this?:

 on: 
   workflow_dispatch: 
   repository_dispatch: 
     types: [trigger_update]
   schedule:
     - cron: '30 2 * * 0,3'

I wonder if we can allow for the schedule and for the trigger at the same time with something like this?:

Hi @kimrutherford. Yes, that looks like it, go ahead. Pretty wild that they are giving all these computing time for free, even allowing users to schedule.

for free

I guess we feed the AI until we make ourselves redundant 🙃

I wonder if we can allow for the schedule and for the trigger at the same time with something like this?:

I struggled to get this to work partly because I wasn't patient enough. After trying a bunch of possibilities it seems to work now.

Hi @kimrutherford. I think I had a similar experience when trying to ping from the CLI to start the action. I did it many times wihtout anything happenning and after a while I had a queue of 10 actions.

	on:
	workflow_dispatch:
	repository_dispatch:
	types: [trigger_update]