@msujew It might not even be possible from forks as the GITHUB_TOKEN only has read permissions for that special case:

https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/

@vince-fugnitto Yeah, I noticed multiple issues already, forks also (unsurprisingly) can't read from our secrets. I'm wondering whether my other idea would be better suited, as it only runs on our repo. The idea was to push to another branch when pushing to master (or merging into it) and merge this one when performing a release.

Anyway, I'm first looking into whether we can force push from Actions to a protected branch, since that would allow us to perform automatic translations after merging and simply amend it to the squashed commit, thereby preserving the history of why translations were added a bit better.

@msujew if we wanted, we can add a workflow_dispatch (so we can manually trigger the CI from the actions page) and do so on release as you mentioned (just need to document it in the release page). We can try to make the CI create pull-request with the updates. I'll leave the final decision up to you however :)

@vince-fugnitto Thanks for the hint! Seems like we also can't push, so automatically creating a PR sounds like the best approach. Works quite well, see msujew#5.

Quick question: Do you have an idea whether there's some Eclipse bot/fake email that's covered by the ECA? I'm using my own for now, but that seems a bit weird to me.

Quick question: Do you have an idea whether there's some Eclipse bot/fake email that's covered by the ECA? I'm using my own for now, but that seems a bit weird to me.

I'm not aware of any bot account :( Is it possible to use the actor?

@JonasHelming are you aware of any bot account in the foundation (covered by the ECA) that we can use to perform the automatic translation updates?

Is it possible to use the actor?

Unfortunately, github.actor only gives us the user name. However, in theory we should be able to get the email (if set) based on the user name by querying the github API. I'll see what I can do.

Anyway, I've also updated the publishing.md in my last push, this is ready for a review.

@vince-fugnitto Running Github API requests inside of actions is surprisingly easy, the action now will always commit using the email of the user that triggered the workflow.

@vince-fugnitto Thanks for the quick review. Please let me know if you find any issues once you run this. Maybe we should run this a day before the release to fix any potential issues?