Skip to content

Rename format pipeline #238

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

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Conversation

illicitonion
Copy link
Collaborator

Our CI checks aren't currently required to merge.

As far as I can tell, this name key is the only thing you can use to describe whether a check is required, and the fact that it matches the name for the other GitHub action means we can't make both required.

Our CI checks aren't currently required to merge.

As far as I can tell, this name key is the only thing you can use to
describe whether a check is required, and the fact that it matches the
name for the other GitHub action means we can't make both required.
Copy link
Collaborator

@shs96c shs96c left a comment

Choose a reason for hiding this comment

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

Let's see if that works

@illicitonion illicitonion enabled auto-merge (squash) January 11, 2024 10:37
@illicitonion illicitonion merged commit 11f98e2 into bazel-contrib:main Jan 11, 2024
@illicitonion illicitonion deleted the rename-format branch January 11, 2024 10:50
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