Repository navigation
feat: ability to lock and replace workflows - #150
Merged
Merged
Conversation
murtaza-u
force-pushed
the
feat/workflow-replace-lock
branch
from
November 5, 2026 16:06
575dcb2 to
fe094b2
Compare
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.
Backstory:
Today the way an agent updates a workflow is by deleting it first. This has couple of problems like,
This PR adds "replace" functionality to address these issues.
Second, this PR also adds the ability to lock workflows. Often when multiple people collaborate with an agent, somebody might unintentionally delete/replace the workflow. To prevent this, workflow can be locked. Lock could be a unlocked in the workflows page.