[thomas-bc-autowot]

Related Issue(s)	#6211
Has Unit Tests (y/n)	n (CI-only change)
Documentation Included (y/n)	n
Generative AI was used in this contribution (y/n)	AI

---

Change Description

Because of the surge of AI contributions, we faced growing CI queue times, and disabled CI on devel pushes, considering PR gates were enough. However we also disabled macOS CI on PR gates, and things started breaking un-noticeably. I suggest we should re-enable a core set of on-push devel CI (framework build/UT and Ref build and INT). This is low-ish cost high impact.

Can always revisit later if it becomes a problem again.

Contributor Checklist

• I have the rights to contribute this change set under the Apache-2.0 license.
• I agree to be bound by the contributor guidelines.

AI Usage (see policy)

Devin (AI) made the workflow edits and ran actionlint, at the direction of Thomas Boyer-Chammard.

• This contribution follows the F´ AI development skills (entered through AGENTS.md).

IAMAI

[github-actions]

Coverage report — base devel

Overall (line): 85.30% → 85.34% (+0.04)
Regression threshold: 0.50% (line).

Regressions

(none over threshold)

Modules changed

Module	Line	Δ	Function	Δ	Branch	Δ
Fw/DataStructures	97.96	+0.09	97.14	+0.00	82.66	+0.18
Os/Generic	90.28	+0.10	89.13	+0.00	75.10	+0.20
Os/Generic/Types	92.14	+0.35	92.86	+0.00	74.77	+0.94
Svc/FpySequencer	86.94	+0.48	99.53	+0.94	79.10	+1.27

New modules

Module	Line	Function	Branch
Fw/Prm	0.00	0.00	0.00

Modules without UTs

CFDP/Checksum/GTest, Drv/LinuxGpioDriver, Drv/LinuxI2cDriver, Drv/LinuxSpiDriver, Drv/Ports/DataTypes, Drv/PosixUartDriver, FppTestProject/FppTest/topology/async, FppTestProject/FppTest/topology/components/Comp, FppTestProject/FppTest/topology/components/Framework, FppTestProject/FppTest/topology/components/Receiver, FppTestProject/FppTest/topology/components/Sender, FppTestProject/FppTest/topology/guarded, FppTestProject/FppTest/topology/sync, FppTestProject/FppTest/topology/top_ports, FppTestProject/FppTest/topology/types, Fw/Com, Fw/Comp, Fw/FilePacket/GTest, Fw/Fpy, Fw/Obj, Fw/Port, Fw/Sm, Fw/Test, Fw/Types/GTest, Os/Models, Svc/Ccsds/Types, Svc/Ccsds/Utils, Svc/FatalHandler, Svc/Subtopologies/CdhCore, Svc/Subtopologies/ComCcsds, Svc/Subtopologies/ComCcsdsSdls, Svc/Subtopologies/ComFprime, Svc/Subtopologies/ComLoggerTee, Svc/Subtopologies/DataProducts, Svc/Subtopologies/DpCompression, Svc/Subtopologies/FileHandling, Svc/Subtopologies/FileHandlingCfdp, Svc/Subtopologies/FileHandlingCfdp/FileHandlingCfdpConfig, TestDeploymentsProject/Ref/DpDemo, TestDeploymentsProject/Ref/PingReceiver, TestDeploymentsProject/Ref/RecvBuffApp, TestDeploymentsProject/Ref/SendBuffApp, TestDeploymentsProject/Ref/Top, TestDeploymentsProject/Ref/TypeDemo, cmake/test/data/TestConfigDeployment, cmake/test/data/TestDeployment/TestBuildAutocoder, cmake/test/data/TestDeployment/TestDuplicateDirective, cmake/test/data/TestDeployment/TestHeaderAutocoder, cmake/test/data/TestDeployment/TestLinkDepends, cmake/test/data/TestDeployment/TestRelative, cmake/test/data/test-fprime-library/TestLibrary/TestComponent, cmake/test/data/test-fprime-library2/TestLibrary2/TestComponent

[thomas-bc]

Circling back on this, with #6218 , the total runtime for a push to devel is ~15-20mins which imo is very much acceptable for the peace of mind of running these on devel again.