[Secure-testing-commits] r58951 - /

[Salvatore Bonaccorso]

Author: carnil
Date: 2017-12-26 19:43:53 +0000 (Tue, 26 Dec 2017)
New Revision: 58951

Modified:
   TODO.gitmigration
Log:
Add more notes for the hook task

Modified: TODO.gitmigration
===================================================================
--- TODO.gitmigration	2017-12-26 18:01:19 UTC (rev 58950)
+++ TODO.gitmigration	2017-12-26 19:43:53 UTC (rev 58951)
@@ -48,6 +48,12 @@
   [18:58] < carnil> is there a way to implement such pre-commit checks with gitlab/salsa?
   [18:58] < Myon> carnil: I think the short answer is "no"
   [18:59] < Myon> the longer answer might include protected branches and runners and stuff
+  [...]
+  [20:15] < formorer> carnil: you answer was probably answered, but no thats not possible. Not allowing random hooks was a design decision because it opens several interesting security consequences
+  [20:17] < formorer> carnil: but if you provide a hook, we can review it and enable it
+  [20:18] < formorer> carnil: see https://docs.gitlab.com/ce/administration/custom_hooks.html for details
+  [20:19] < formorer> hope that helps
+  [20:27] < formorer> carnil: https://wiki.debian.org/Salsa/Doc#Custom_Hooks
 
 security-team.debian.org website