Infrastructure | Add support for developer signed commits (#126)

[Amar Takhar (@amar)]

Issue created by Amar Takhar: https://gitlab.rtems.org/administration/infra/-/work_items/126



We need to have signed commits from developers who are identified personally.  They key of trust we'll keep is important and we'll build it over time.

This ensures that commits originate from the developer who can unlock the key.  Whether they use an agent with a memory preserved unlocked key or otherwise it still states it that it came from their workstation.

We will be moving to this in the future there is no date set because we need to implement this in the least impactful way possible.  There is a lot of other groundwork that needs to be done including signed releases with no funding it will be very slow but it's on the horizon.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/infra/-/work_items/126
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-awi04cbpac2uhfxo6gppmtatu-20/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260815/c7ab2e17/attachment-0001.htm>