Update Bundle Naming Convention and Add Task Locking Endpoints #1163
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
CollinBeczak
changed the title
CollinBeczak
force-pushed
the
update-update-bundle-naming-convention
branch
from
0959651 to
5e0fa47
Compare
|
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.
This PR includes the following enhancements and changes:
Bundle Naming Convention:
Replaces resetTaskBundle with updateTaskBundle for better clarity and consistency in naming.
New Task Locking Endpoints:
Adds endpoints to lock, unlock, and refresh locks on multiple tasks at once. These endpoints are critical for efficiently handling task bundle locking.
Introduced new endpoints: