[CHORE] Does the process and data in Elsa 3.1.3 designer return to the previous node or to the original node after approval rejection? How is it specifically implemented? #345
This file contains 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
| 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 | |
| }); |