Buildozer not working #456
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
| # When a user creates an issue that is actually a support request, it should | |
| # be closed with a friendly comment. | |
| # | |
| # This triggers on an issue being labelled with the `support` tag. | |
| name: 'Support Requests' | |
| on: | |
| issues: | |
| types: [labeled, unlabeled, reopened] | |
| permissions: | |
| issues: write | |
| jobs: | |
| action: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: dessant/support-requests@v4 | |
| with: | |
| github-token: ${{ github.token }} | |
| support-label: 'support' | |
| issue-comment: > | |
| 👋 @{issue-author}, | |
| Sorry to hear you are having difficulties with Kivy's Buildozer; Kivy unites a number of different technologies, so building apps can be temperamental. | |
| We try to use GitHub issues only to track work for developers to do to fix bugs and add new features to Buildozer. This issue has been closed, because it doesn't describe a bug or new feature request for Buildozer. | |
| There is a mailing list and a Discord channel to support Kivy users debugging their own systems, which should be able to help. They are linked in the [ReadMe](https://github.com/kivy/buildozer#support). | |
| Of course, if it turns out you have stumbled over a bug in Buildozer, we do want to hear about it here. The support channels should be able to help you craft an appropriate bug report. | |
| close-issue: true | |
| lock-issue: false |