If one wants to avoid software with AI code then being aware which MRs need replacing helps. However, accepting it encourages it more and makes it less fesible that you could prune all the MRs written in part by AI. Disclosing it will become worthless if it becomes the norm.
If the code is good I don’t have an issue with it being merged even if ai was used, that being said I bet the obvious outcome is that either people ignore the policy and nothing changes or they comply and most reviewers focus on the non-ai group which is how it was before ai. All in all, this decision can never hurt the development, since as far as I am aware there is no requirement to review an MR.
If one wants to avoid software with AI code then being aware which MRs need replacing helps. However, accepting it encourages it more and makes it less fesible that you could prune all the MRs written in part by AI. Disclosing it will become worthless if it becomes the norm.
If the code is good I don’t have an issue with it being merged even if ai was used, that being said I bet the obvious outcome is that either people ignore the policy and nothing changes or they comply and most reviewers focus on the non-ai group which is how it was before ai. All in all, this decision can never hurt the development, since as far as I am aware there is no requirement to review an MR.