Deprioritize is exact-target; repeat-DELETE is a no-op - #428
Merged
Conversation
Mirrors bc3 #12483 (d0edc128): the DELETE clears only the priority carried by the recording the URL identifies, deleting an absent priority is a no-op 204, and surfaced steps are addressed by their priority_recording_id.
jeremy
added a commit
that referenced
this pull request
Jul 31, 2026
* origin/master: Deprioritize is exact-target; repeat-DELETE is a no-op (#428)
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
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.
Mirrors basecamp/bc3#12483 (merged as
d0edc128): the priorities DELETE clears only the priority carried by the recording the URL identifies, deleting an absent priority is a no-op204, and card table steps surfaced under their parent card are addressed by theirpriority_recording_id.Synced from bc3
doc/api/byscript/api/sync_to_bc3_api— not a hand-edit.