Minor: Trigger docs CI build on changes to asf.yaml #5726
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
core
alamb
commented
Mar 24, 2023
| @@ -511,7 +511,7 @@ async fn prune_periods_in_column_names() { | |||
| Scenario::PeriodsInColumnNames, | |||
| "SELECT \"name\", \"service.name\" FROM t WHERE \"service.name\" = 'frontend' AND \"name\" != 'HTTP GET / DISPATCH'", | |||
| Some(0), | |||
| Some(2), // prune out middle and last row group | |||
| Some(2), // prune out middle and last row group | |||
alamb
changed the title
viirya
approved these changes
Mar 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Related to #5500
Rationale for this change
Publishing the docs is configured by
asf.yamland thus if that files changes we should also retrigger the docs workflowAs suggested by @kou on #5703 (review)
What changes are included in this PR?
Are these changes tested?
No
Are there any user-facing changes?
No