[GH-ISSUE #303] Break up linting and testing into two separate groups, possibly a third - monitoring #677

New Issue

GiteaMirror · 2026-04-15T04:00:38-05:00

GiteaMirror commented

2026-04-15 04:00:38 -05:00

Originally created by @jessicalostinspace on GitHub (Jan 18, 2020).
Original GitHub issue: https://github.com/sdras/awesome-actions/issues/303

Linting and Testing should be two separate groups with possible sub groups. For example: under linting, each language could be split into subgroups or a groupd like "reviewdog" which has several entries not grouped together under the linting category. Monitoring could also be separated out to its own group (ie. scanning code quality, code coverage, etc). "Scan git commits for secrets with gitleaks" and "Scan for secrets in your source code" should also be moved to "Security" group.

Originally created by @jessicalostinspace on GitHub (Jan 18, 2020). Original GitHub issue: https://github.com/sdras/awesome-actions/issues/303 Linting and Testing should be two separate groups with possible sub groups. For example: under linting, each language could be split into subgroups or a groupd like "reviewdog" which has several entries not grouped together under the linting category. Monitoring could also be separated out to its own group (ie. scanning code quality, code coverage, etc). "Scan git commits for secrets with gitleaks" and "Scan for secrets in your source code" should also be moved to "Security" group.

GiteaMirror closed this issue

2026-04-15 04:00:39 -05:00

GiteaMirror commented

2026-04-15 04:00:39 -05:00

@gep13 commented on GitHub (Jan 18, 2020):

@jessicalostinspace this makes a lot of sense to me. Would you be in a position to send in a PR to make these changes?

@gep13 commented on GitHub (Jan 18, 2020): @jessicalostinspace this makes a lot of sense to me. Would you be in a position to send in a PR to make these changes?