You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Occasionally, when I edit a referenced action version, a warning about the non-existing version appears during editing and doesn't disappear after finishing the edit. For example, I changed the action from slidoapp/[email protected] to slidoapp/[email protected] by deleting "2.0" and replacing it with "3.1". However, the warning got stuck on "Unable to resolve action slidoapp/[email protected], repository or version not found." Even closing and reopening the workflow file didn't help, I had to restart VSCode to get rid of that warning message.
To Reproduce
Difficult to reproduce, it happens randomly while editing the referenced actions
Expected behavior
After finishing the edit, the plugin re-checks the existence of the final version of the action being edited (v3.1.0, not v.0.0).
Screenshots
Extension Version v0.27.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Occasionally, when I edit a referenced action version, a warning about the non-existing version appears during editing and doesn't disappear after finishing the edit. For example, I changed the action from
slidoapp/[email protected]
toslidoapp/[email protected]
by deleting "2.0" and replacing it with "3.1". However, the warning got stuck on "Unable to resolve action slidoapp/[email protected], repository or version not found." Even closing and reopening the workflow file didn't help, I had to restart VSCode to get rid of that warning message.To Reproduce
Difficult to reproduce, it happens randomly while editing the referenced actions
Expected behavior
After finishing the edit, the plugin re-checks the existence of the final version of the action being edited (
v3.1.0
, notv.0.0
).Screenshots
Extension Version
v0.27.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: