Skip to content

Commit

Permalink
Attempting to fix "no text" error
Browse files Browse the repository at this point in the history
  • Loading branch information
CodeByDrescher committed Jan 31, 2025
1 parent e9b00be commit f7c3711
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/NightlyBMDB_CLI.yml
Original file line number Diff line number Diff line change
Expand Up @@ -376,7 +376,7 @@ jobs:
path: ${{ github.workspace }}/tracer.json

- name: Post results to slack part 1 (report.md from exec-report CLI command)
run: curl -X POST -F token="${{ secrets.SLACK_BOT_TOKEN }}" -F channel=${{ secrets.SLACK_CHANNEL_VCELL_DEV_TOKEN }} -F text="```$(cat ${GITHUB_WORKSPACE}/report.md)```" https://slack.com/api/chat.postMessage
run: curl -X POST -F token="${{ secrets.SLACK_BOT_TOKEN }}" -F channel=${{ secrets.SLACK_CHANNEL_VCELL_DEV_TOKEN }} -F text="BMDB Results:\n\`\`\`$(cat ${GITHUB_WORKSPACE}/report.md)\`\`\`" https://slack.com/api/chat.postMessage

# Not currently working
- name: Post results to slack part 2 (sound alarm if changed results)
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/NightlyPublished_CLI.yml
Original file line number Diff line number Diff line change
Expand Up @@ -376,7 +376,7 @@ jobs:
run: echo "$(cat ${GITHUB_WORKSPACE}/report.md)"

- name: Post results to slack part 1 (report.md from exec-report CLI command)
run: curl -X POST -F token="${{ secrets.SLACK_BOT_TOKEN }}" -F channel=${{ secrets.SLACK_CHANNEL_VCELL_DEV_TOKEN }} -F text="```$(cat ${GITHUB_WORKSPACE}/report.md)```" https://slack.com/api/chat.postMessage
run: curl -X POST -F token="${{ secrets.SLACK_BOT_TOKEN }}" -F channel=${{ secrets.SLACK_CHANNEL_VCELL_DEV_TOKEN }} -F text="Published Results:\n\`\`\`\n$(cat ${GITHUB_WORKSPACE}/report.md)\n\`\`\`" https://slack.com/api/chat.postMessage

# Not currently working
- name: Post results to slack part 2 (sound alarm if changed results)
Expand Down

0 comments on commit f7c3711

Please sign in to comment.