appleboy / appleboy/telegram-action
APK not deploy
- Dominant language
- Dockerfile
- Stars
- 1k
- Forks
- 126
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
.
.
//Build process
- uses: actions/upload-artifact@v2
with:
name: build-Android
path: ${{ github.workspace }}/build/Android
.
.
.
.
- name: Checkout code
uses: actions/checkout@v2
- uses: actions/download-artifact@v2
with:
name: build-Android
path: ${{ github.workspace }}/build/Android
- name: send telegram message
uses: appleboy/telegram-action@master
with:
to: ${{ secrets.TELEGRAM_ID }}
token: ${{ secrets.TELEGRAM_TOKEN }}
message: Файлы загружены на диск (${{ secrets.APP_NAME }})
document: ${{ github.workspace }}/build/Android/test.apk
_________________________________________________________________________________
Telegram sends only the text of the message, no errors
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the GitHub Actions steps shown for upload-artifact, download-artifact, and appleboy/telegram-action, checking whether build/Android/test.apk exists at the document path when the Telegram step runs. Reproduce the workflow and verify that the completed behavior includes the APK as a Telegram document, not only the message text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100