Skip to content

Conversation

carlopi
Copy link
Contributor

@carlopi carlopi commented Oct 16, 2024

Connected to conversation at #14384 (comment).

Basically logic after the PR will be as follow:

on main or feature: do complete check
else: do check only the diff.

Note that feature is not triggered automatically (not even on nightly), so this will have no difference as is, but allows this to be triggered manually and check the results.

Independently to be reviewed what should run on nightly.

@carlopi
Copy link
Contributor Author

carlopi commented Oct 16, 2024

For example I triggered on my fork https://github.com/carlopi/duckdb/actions/runs/11362829776 a complete run on feature (after tentatively already merging this :) ), to check whether this works (I would expect so) and to discover what is currently off.

@Mytherin
Copy link
Collaborator

Thanks! Looks like the linked CI run is failing in your fork for reasons unrelated to the tidy checks themselves. Could you have a look?

@carlopi carlopi force-pushed the tidy_check_complete_of_feature branch from 7d26a56 to c4dc3d5 Compare October 16, 2024 10:32
@duckdb-draftbot duckdb-draftbot marked this pull request as draft October 16, 2024 10:32
@carlopi carlopi marked this pull request as ready for review October 16, 2024 10:33
@carlopi
Copy link
Contributor Author

carlopi commented Oct 16, 2024

New run eventually: https://github.com/carlopi/duckdb/actions/runs/11363878681

I will later check.

@Mytherin Mytherin merged commit 9a846d8 into duckdb:feature Oct 16, 2024
7 checks passed
@Mytherin
Copy link
Collaborator

Thanks!

@carlopi carlopi deleted the tidy_check_complete_of_feature branch October 16, 2024 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants