Each time a task associated to the Slicer internationalization is automated by the execution of a script on a machine, the machine user running such script will be identified as
Type of Sliceri18nBot
This Sliceri18nBot user can commit changes to a defined subset of Slicer repositories. The associated GitHub account is sliceri18nbot and it can commit changes to all repositories associated with the
sliceri18nbot team in the Slicer GitHub organization.
As documented on managing deploy keys Github guide, there are multiple approaches to grant a machine access to a repository. We chose the machine user one.
In a nutshell, the steps to configure a git machine user are:
- Generate SSK keys without pass-phrase:
ssh-keygen -t rsa -C "email@example.com"
- Add the generated
id_rsa.pubkey to the list of SSH keys associated with sliceri18nbot user. Each key *SHOULD* be named
sliceri18nbot-<hostname>. For example
- Setup git username and email:
git config --global user.name "Slicer i18n Bot" git config --global user.email "firstname.lastname@example.org"
This Sliceri18nBot user publishes update in a branch associated with https://github.com/Slicer/SlicerLanguagePacks
As of 2022-01-25, the machines with Sliceri18nBot accounts are: