Formalize process for PRs that require changes on test repos

[thomas-bc]

F´ Version
Affected Component

---

Feature Description

CI now runs checks on external repositories such as https://github.com/fprime-community/fprime-workshop-led-blinker
When a user makes a PR that proposes a change that requires a change of how to use F´, this will result in breakage of the CI.

For now, we have a devel branch where users can make a PR and make the appropriate change (e.g. see fprime-community/fprime-workshop-led-blinker#38)
This becomes weird because we want master to host the latest docs, and devel to host the compatible version with devel of core F´... which leads to master and devel diverging.

Let's formalize (maybe rework?) and capture that process.

[thomas-bc]

An idea: devel has connotations that do not match our usage of the branch, unless we want the latest docs to be on devel as well. In that case, the argument could be made that we do not need the master branch on the tutorial repositories either. And we can make formal releases of each tutorials as well. But that will make the number of releases to be released on each release (lol) grow substantially.... not ideal.

If we want to keep a split of between main and a "devel" state, we could rename devel on the tutorials to be more meaningful, e.g. pr-checks or something. That branch would only be for validating PR changes on core F´. And we can merge that branch with a merge commit on each F´ release.

[thomas-bc]

This also begs the question... how do we manage cases where 2 PRs are reviewed at the same time, and both require changes. We can't merge both into the tutorial's devel cause they will break each other...

[thomas-bc]

It also brings up a semi-concern. The current approach is to merge things into the tutorial's devel without really having fully reviewed/approved the changes that are going in there. That sounds a little odd to me.

[thomas-bc]

The above 2 comments lead me to believe that we may want to find a mechanism to have the CI run on ad-hoc branches, or at least re-label devel to something else.

[thomas-bc]

Completed, see https://github.com/nasa/fprime/pull/2289/files#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055