Acrually we normally use License eye to generate and fix the headers and we have the checks in Place basically in all the other repositories at the Github action level on PRs. Again it was a mistake to comit this code drop without fixing the headers first. -- Michele Sciabarra mich...@sciabarra.com
----- Original message ----- From: PJ Fanning <fannin...@apache.org> To: dev@openserverless.apache.org Subject: commit policy? Date: Monday, December 09, 2024 9:40 PM Hi, Would it be possible to come up with a code of practice detailing basics like: * required license headers and code style generally * merging one's own PRs - which is strongly discouraged in most PMCs - eg https://github.com/apache/openserverless-streamer/pull/2 * allowing some time for PRs to be reviewed I think it is important for PPMCs to have some written guidelines for how code is submitted and then committed. Regards, PJ
