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

Move linting to a separate GitHub Actions workflow #17267

Merged
merged 1 commit into from
Nov 12, 2023

Conversation

Snuffleupagus
Copy link
Collaborator

This way we introduce more parallelism in the GitHub Actions tests, which should reduce overall runtime and thus cannot hurt.

This way we introduce more parallelism in the GitHub Actions tests, which should reduce overall runtime and thus cannot hurt.
@timvandermeij timvandermeij merged commit e0e5be2 into mozilla:master Nov 12, 2023
6 checks passed
@timvandermeij
Copy link
Contributor

Thank you for doing this; it's in line with the plan I also had to move every target into its own workflow because it increases parallelism and makes it easier to spot what failed without having to go through logs.

@Snuffleupagus Snuffleupagus deleted the lint-workflow branch November 12, 2023 12:11
@Snuffleupagus
Copy link
Collaborator Author

Thank you for doing this; it's in line with the plan I also had to move every target into its own workflow because it increases parallelism and makes it easier to spot what failed without having to go through logs.

Agreed, nice that we've been thinking the same thing here :-)


@calixteman Can you please mark the new "Lint" workflow as Required, so that we cannot accidentally land something that fails linting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants