[TODO]: update generated models from apify-docs PR #2622#860
Closed
apify-service-account wants to merge 1 commit into
Closed
[TODO]: update generated models from apify-docs PR #2622#860apify-service-account wants to merge 1 commit into
apify-service-account wants to merge 1 commit into
Conversation
apify-service-account
added
the
t-tooling
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #860 +/- ##
==========================================
- Coverage 94.82% 94.49% -0.34%
==========================================
Files 48 48
Lines 5045 5069 +24
==========================================
+ Hits 4784 4790 +6
- Misses 261 279 +18
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
vdusek
approved these changes
Jun 17, 2026
Contributor
|
false positive, triggered by merging the master commit to PR |
vdusek
added a commit
that referenced
this pull request
Jun 17, 2026
…861) The `Regenerate models` workflow opened [#860](#860), duplicating webhook fields already merged via [#855](#855). The **Set up branch** step regenerated on top of a stale `update-models-docs-pr-<N>` branch (based on a pre-#855 `master`), so an already-merged change reappeared as a fresh diff. Fix: always regenerate against the current `master`. - **Check for model changes** compares the regenerated files against `master` and skips when there is no diff, so an already-merged change can no longer produce a duplicate PR. - When there is a diff, the branch is force-pointed at `master` and `signed-commit` adds one regenerated commit on top. The PR still updates whenever the source docs PR gets new commits. Trade-off: the branch is always a single regenerated commit on top of `master`, so any commits pushed onto it directly are replaced on the next run. This is the intended, idempotent behavior for an auto-generated branch.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR updates the auto-generated Pydantic models and TypedDicts based on OpenAPI specification changes in apify-docs PR #2622.