meta-ros: superflore branches question ? #1244
-
|
Hello, community! Philosophical question: When a new branch is created via the Examples What is the correct approach or procedure when deciding to update your meta-ros and change branches in order to avoid manually redoing the bbappend files? When someone in the community creates a new branch Or would you like me to provide a patch to fix it, for example? My goal is just to clarify the process when using a community generated superflore branch. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Can I help you with testing or anything else? |
Beta Was this translation helpful? Give feedback.
Sorry for the delayed response. I haven't been getting notifications on Discussion entries. I think I may have fixed that now.
I personally use the rename-bbappends.sh script with the name of the layer and the latest "sync" commit
scripts/rename-bbappends.sh meta-ros2-humble 6c1f040d792b15073e4e13fcb72712303d685f6dHowever, I don't merge the community generated superflore branches. Since I have automated it in GitHub Actions to take less than 20 minutes, it is easier for me to re-run superflore myself rather than do a code review on the generated recipes.
Ideally, I would love to fully automate the whole process by having a scheduled CI script check for upstream ROS syncs. With the GitLab…