Add a "lock-for-agent" optional boolean field to the on.issue field in the front matter.
on:
issue:
lock-for-agent: true
When enabled, the issue is locked while the agent job runs and unlocked in the conclusion. This prevents concurrent updates to the issue while it is being analyzed.
If enabled, the compiler should emit a step in the activation job to lock the issue in context . Use a JavaScript script, from an embedded file registered with the bundler. Do not provide a reason.
If reaction is enabled, add a message that the issue is locked.
If enabled, the conclusion job should unlock the issue even on failure. Use JavaScript, separate file, registered with bundle.
Add a "lock-for-agent" optional boolean field to the on.issue field in the front matter.
on:
issue:
lock-for-agent: true
When enabled, the issue is locked while the agent job runs and unlocked in the conclusion. This prevents concurrent updates to the issue while it is being analyzed.
If enabled, the compiler should emit a step in the activation job to lock the issue in context . Use a JavaScript script, from an embedded file registered with the bundler. Do not provide a reason.
If reaction is enabled, add a message that the issue is locked.
If enabled, the conclusion job should unlock the issue even on failure. Use JavaScript, separate file, registered with bundle.