### Problem to solve Avoid CI pipeline creation each time a suggestion is applied ### Intended users Everyone using documentation as code feature ### Further details When writing articles or documentation using markup language with CI environments (for review and production) it is very common to have a long list of comments with suggestions. The "apply suggestion" is great but in this context it is very time and resource consuming to create a pipeline per suggestions applied. ### Proposal It may be solved by adding a checkbox to the suggestion UI adding `[skip-ci]` to the commit message. Or maybe more globally to the project settings? ### Permissions and Security Every one having the ability to interact with a proposal must be able to skip the pipeline creation. ### Documentation TODO ### Testing Don't see any risk associated ### What does success look like, and how can we measure that? Runner usage must decrease if used. It is definitely a green action, so people dependent. ### What is the type of buyer? NA ### Links / references