[casparvl]

Whenever the tip of EESSI/software-layer-scripts' main branch changes, this GH action is started. The only thing this GH action does is send a trigger to a GH action in EESSI/software-layer (added in EESSI/software-layer#1568 ), which in turn will update the bot/software_layer_scripts_commit in a feature branch, and create a PR.

This effectively provides an auto-update mechanism for bot/software_layer_scripts_commit with human oversight and minimal security impact.

[boegel]

@casparvl is this still relevant?

[casparvl]

Meh, this would have allowed for event-based updating of the software_layer_scripts_commit has in EESSI/software-layer/bot/software_layer_scripts_commit, which would have been nice to have. Currently, it's updated by CI that runs on a 1-hour schedule.

Honestly, while I think the event-based approach is nicer, it may be a bit overkill here. And it would require a token that allows starting/stopping CI from software-layer. That's not a huge deal from a security perspective, but it's not nothing either. Since the current hourly runs work fine in practice:

• no one is annoyed if the commit hash is outdated (unless they need some new feature from software-layer-scripts, but then they typically know and update the commit hash manually in their own PR)
• the biggest latency is probably introduced by us having to merge the auto-generated commit-updates - not the PR being created on the hourly schedule

I'll close this.

[bedroge]

Also note that you can start this workflow manually at https://github.com/EESSI/software-layer/actions/workflows/update_software_layer_scripts_commit.yml in case you really need it quickly.