[Docs] Update per-task profile persistence resume behavior#16
Draft
zoomote[bot] wants to merge 1 commit into
Draft
[Docs] Update per-task profile persistence resume behavior#16zoomote[bot] wants to merge 1 commit into
zoomote[bot] wants to merge 1 commit into
Conversation
Author
|
1 issue outstanding. See task
Reviewed 6bfc3de |
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.
What changed
Updated the "Reopening from history" bullet in the Per-Task Profile Persistence section of the API Configuration Profiles page. It previously stated that resuming a task from history always restores the task's original profile even after the user changed the global selection; it now states that resuming honors the current global profile selection and remembers it going forward.
Why this change was made
Paired documentation for the Zoo-Code fix for issue #970: restoring a task no longer reverts the provider profile the user switched to after stopping the task, so the docs describing the old restore behavior had to be updated to match.
Impact
Documentation now accurately describes the resume/restore behavior. No functional change in this repository.
Screenshots
Related PRs