Repository navigation
Refresh Intercom company deletion description - #104
Merged
Merged
Conversation
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
1 participant
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.
Refresh Intercom’s official public 2.16 artifact with its clarification of
DELETE /companies/{company_id}. The description now says the company record remains in the workspace, all contacts are detached without deleting the contacts, detachment cannot be reversed, and changes may take time to appear. This matches the vendor’s published change #697.168 paths / 235 operations remain unchanged; no added or removed endpoints, schema changes or security changes. Keep both existing version directories. The importer selects 2.16 from the numeric public-release catalog at the same pinned SHA, excluding the preview
0directory, and replays the two previously documented exact reporting-path parameter fixes.Source: pinned official YAML, commit
7b3a218f2b8a9c09ae24247270c764444cddaf70, entry SHA-256e007fe1902ceaa64e6dbaedfc064f2a2e4fc24bab6c86cf1c8f6900c2b0c42ca. Provenance and patch recipe hashes remain in the file’s info block. No OpenAPI version conversion.Validation: full OpenAPI validation, all references, required path parameters, responses and YAML value/type round-trip pass. Parsed content differs from the previous import in exactly one vendor description plus updated provenance; existing curation and the historical 2.14 file are retained. Source repository health was checked before import.