We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github CI job names are categorised into two groups:
.github/workflows/coverage.yml:name: Coverage .github/workflows/checks.yml:name: Checks .github/workflows/speed-benchmarks.yml:name: Speed benchmarks .github/workflows/performance-benchmarks-naslib.yml:name: Performance Benchmarks with NASLib .github/workflows/tests-integration.yml:name: Tests (Integration) .github/workflows/pypi-publish.yml:name: Publish distributions to PyPI or TestPyPI .github/workflows/tests-storage.yml:name: Tests (Storage with server) .github/workflows/performance-benchmarks-bayesmark.yml:name: Performance benchmarks with bayesmark .github/workflows/tests.yml:name: Tests .github/workflows/performance-benchmarks-mo-kurobako.yml:name: Performance Benchmarks with kurobako for multi-objective optimization .github/workflows/tests-with-minimum-versions.yml:name: Tests with minimum versions .github/workflows/checks-integration.yml:name: Checks (Integration) .github/workflows/sphinx-build.yml:name: Sphinx .github/workflows/reviewdog.yml:name: Reviewdog .github/workflows/dockerimage.yml:name: Build Docker Image .github/workflows/performance-benchmarks-kurobako.yml:name: Performance Benchmarks with kurobako
-
.github/workflows/mac-tests.yml:name: mac-tests .github/workflows/windows-tests.yml:name: windows-tests .github/workflows/stale.yml:name: stale
I believe that unifying names makes the reviewers more developer-friendly. letters
Rename the second group to match the first group naming rule.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Motivation
Github CI job names are categorised into two groups:
-
instead ofI believe that unifying names makes the reviewers more developer-friendly. letters
Description
Rename the second group to match the first group naming rule.
Alternatives (optional)
No response
Additional context (optional)
No response
The text was updated successfully, but these errors were encountered: