Skip to content
New issue

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

feat: Add benchmark scope #7

Merged
merged 2 commits into from
Sep 2, 2024
Merged

feat: Add benchmark scope #7

merged 2 commits into from
Sep 2, 2024

Conversation

tomi
Copy link

@tomi tomi commented Aug 20, 2024

The benchmark scope is meant for the benchmark cli.

The benchmark scope is meant for the benchmark cli.
@@ -9,7 +9,7 @@ const TYPES = [
"ci",
];

const SCOPES = ["API", "core", "editor"];
const SCOPES = ["API", "core", "editor", "benchmark"];
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. What is the criteria for adding a new scope instead of using test or ci? Existing scopes are broad while benchmark seems granular.
  2. If we decide to add a new scope, can we add a test?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test and ci define the type of the commit, scope defined the component it is for. So we could have e.g. ci(benchmark). We could also consider the benchmarks to be just tests for the cli (i.e. always test(core)) or not use a scope at all. It is its own package and application, so I think it would make sense to have a separate scope for it.

@tomi tomi requested a review from ivov September 2, 2024 08:25
@ivov
Copy link

ivov commented Sep 2, 2024

Please remember this needs to be published for changes to take effect.

@tomi tomi merged commit 8e0184e into master Sep 2, 2024
2 checks passed
@tomi tomi deleted the feat-add-benchmark-scope branch September 2, 2024 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants