RTEMS | Export Issues from Coverity Scan (#3948)
MITHILESH MATTAPALLI (@mithileshm)
gitlab at rtems.org
Sat Jan 10 17:35:33 UTC 2026
MITHILESH MATTAPALLI commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/3948#note_138411
Agreed regarding the "issue graveyard" risk. I will design the script to handle full synchronization:
1. Creation: Open new issues for CIDs present in the CSV but missing from GitLab.
2. Auto-Closure: Close existing GitLab issues if their CID is missing from the current CSV (implying the defect is fixed).
I have successfully parsed the export (130 defects). Before implementing the API calls, do we have a sandbox repository where I can test this logic safely?
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/3948#note_138411
You're receiving this email because of your account on gitlab.rtems.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260110/744db68f/attachment-0001.htm>
More information about the bugs
mailing list