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

[GHA] Configure license check #591

Closed
wants to merge 2 commits into from
Closed

Conversation

FranzBusch
Copy link
Member

No description provided.

@FranzBusch FranzBusch force-pushed the fb-gha-license-check branch from 9ac5f70 to 2c615f2 Compare July 12, 2024 10:09
@FranzBusch FranzBusch force-pushed the fb-gha-license-check branch from 2c615f2 to 1168b15 Compare July 12, 2024 10:10
@FranzBusch FranzBusch force-pushed the fb-gha-license-check branch from 0bf134f to 9d7b6e8 Compare July 12, 2024 13:42
Comment on lines +12 to +13
unacceptable_language_check_enabled: false
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are we doing opt-out? Seems like it might be pretty bad to do that since we'll introduce CI breakages for adopters of the reusable workflow when we add new things that they don't want and/or can't use for some reason.

Copy link
Contributor

Choose a reason for hiding this comment

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

Adopters can lock to a specific commit hash, I believe, instead of depending on main.

I think it's fair to discuss which steps are opt-out (those that we expect/want all repos to have) and opt-in (optional steps that only some repos need).

@FranzBusch FranzBusch closed this Jul 24, 2024
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.

3 participants