Skip to content

[BUG]Elsa 3.1.3 uses a visual designer to implement workflow approval. When a node approval is rejected, the process cannot return to the previous node or the original node? #348

[BUG]Elsa 3.1.3 uses a visual designer to implement workflow approval. When a node approval is rejected, the process cannot return to the previous node or the original node?

[BUG]Elsa 3.1.3 uses a visual designer to implement workflow approval. When a node approval is rejected, the process cannot return to the previous node or the original node? #348

Workflow file for this run

name: Append Footer to Issue with Bounty Label
on:
issues:
types: [labeled]
jobs:
append-footer:
if: github.event.label.name == 'bounty'
runs-on: ubuntu-latest
steps:
- name: Checkout repo
uses: actions/checkout@v2
- name: Read Footer Content
id: footer
uses: jaywcjlove/github-action-read-file@main
with:
path: docs/bounty-footer.md
- name: Append Footer to Issue
uses: actions/github-script@v7
with:
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const issueComment = `${{ steps.footer.outputs.content }}`;
await github.rest.issues.createComment({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
body: issueComment
});