run script in all repos

[maryliag]

Test run was successful with only a few repos. It was also tested with multiple executions and no new PR was created (as expected).

PRs generated:
open-telemetry/opentelemetry-java#8347
open-telemetry/opentelemetry-js#6649
open-telemetry/opentelemetry-js-contrib#3500

Now this PR remove the list of repos, so it can be executed in all repos under the org open-telemetry

[thompson-tomo]

@maryliag this run appears to have a couple of edge cases:

• some teams use * for list so markdownlint fails. Should the guidance be to use -?
• some documents are not having names being removed & instead they are just being added to emeritus ie chore: Move inactive members to emeritus opentelemetry-cpp-contrib#611

[martincostello]

• some teams use * for list so markdownlint fails. Should the guidance be to use -?

Not every repo has the same lint requirements so I don't think we can make everyone happy - SIGs can fix-up PRs if they want to proceed with merging them.

some documents are not having names being removed

Everyone's documents are different - again, SIGs can fix-up anything extra.

[thompson-tomo]

Yes but there was a completed attempt to standardise the contributing section across all repos #2830

[martincostello]

So for the sake of one list in one file everyone needs to change the markdown linting rules for their entire repo?

[thompson-tomo]

No i didn't suggest that. I am purely talking about the sections which this script is changing/managing.

The most likely scenario I see would be to suppress the violation of that markdownlint rule within a section of the doc. Then within that section have it as a - so that alphabetical sorting etc works.

[maryliag]

@thompson-tomo ideally all readmes would use -. If the repo wants to update to that, great, otherwise I won't enforce this.
I'm adding an update to the script to deal with both scenarios (* and -), which is why some nomes did not got removed, because the script didn't recognize the pattern with *. If there are open PRs with this issue, feel free to commit any fixes and following iterations should handle properly

[thompson-tomo]

Thanks @maryliag just for completness it might be worthwhile to also cater for the + symbol which is a valid list character -> https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md004---unordered-list-style