From: Scott Weaver on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2732#note_1739120434 Hi @dzickusrh. I was playing with your rt merge script and I wasn't sure what the initial conditions should be. Is this what you had in mind? ``` git checkout -b master-rt-devel linux-rt-devel/linux-6.7.y-rt git branch os-build-rt-devel git branch os-build-automotive-devel ``` But there was an error when I ran the script because `os-build-rt-automated` didn't exist. Should the script create that since it sounds like a temporary branch? Once I create that branch (based on `os-build-rt-devel`) I think everything worked as expected. Also, the remote to `linux-rt-devel` will be created in `.gitlab-ci.yaml`? I guess maybe that's where `os-build-rt-automated` will get created. Just a nit, but in order to see that I needed to create a gitlab remote I moved the `set -e` to after you source `ark-ci-env.sh` or it fails quietly. I also removed the `TO_PUSH` check in `ci_pre_check()` so the error gets printed (I don't want to set `DIST_PUSH`). -- _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
