workflows: Add workflow for syncing module with upstream#266
Conversation
| target_repository: "zephyrproject-rtos/lvgl" | ||
| target_branch: "master" | ||
| secrets: | ||
| PAT_TOKEN: ${{ secrets.ZB_REPO_SYNC_GITHUB_TOKEN }} |
There was a problem hiding this comment.
Related: Do we envision one token with write permissions to all the module repos, or a dedicated token per repo? If dedicated, this should probably be named with the module name included.
There was a problem hiding this comment.
Related: Do we envision one token with write permissions to all the module repos, or a dedicated token per repo? If dedicated, this should probably be named with the module name included.
There will be one token for all automated repository sync workflows -- there is not much point in having dedicated token per repo when any workflow in this repository can access all repository secrets.
There was a problem hiding this comment.
From my POV this is still a good solution overall.
For the exact details of the implementation, I think it is best if @stephanosio (i.e. somebody who actually takes care of the infrastructure) decides on.
|
@stephanosio any updates? this came up for another repo ( |
stephanosio
left a comment
stephanosio
left a comment
There was a problem hiding this comment.
@faxe1008 If you prefer, I could also make the necessary changes myself and merge this PR to expedite the process a bit (there will likely be more changes necessary as I test this).
|
hal_ethos and maybe cmsis_6 in the future would really benefit from this in the future |
|
@stephanosio I will incorporate the changes you suggested and then you can take it from there. |
Since some modules owned by the Zephyr organization are not created as a Github fork maintaining them as a complete mirror requires manual pushing. To fix this add a reusable workflow that can be configured for each module to sync a specific branch in our version with upstream. Also adds a sample usage of said workflow for the LVGL module. Signed-off-by: Fabian Blatz <fabianblatz@gmail.com>
faxe1008
force-pushed
the
add_sync_jobs
branch
from
08dddbf to
e58adcc
Compare
|
@stephanosio applied your suggestions, feel free to take over :^) |
|
@stephanosio did you find some time to check this one out? I know there were some concerns in regards to token scoped access, right? |
|
@stephanosio ping |
6 participants
Since some modules owned by the Zephyr organization are not created as a Github fork maintaining them as a complete mirror requires manual pushing. To fix this add a reusable workflow that can be configured for each module to sync a specific branch in our version with upstream. Also adds a sample usage of said workflow for the LVGL module.