If you are asking for help from the Drone community of volunteers this guide will help you submit an issue with sufficient information for us to help you.
Provide your Yaml File
Please submit your .drone.yml file with sensitive information redacted. If a plugin or build step is not working as expected this is usually due to a configuration problem. Without access to the Yaml we are left to speculate, and this prolongs the troubleshooting process.
Provide Build Logs
Please submit your build logs, if applicable. The full build logs may contain information as to why the build fails (especially if you forgot to update your yaml checksum).
Provide Server Logs
Please submit your server logs, if applicable. If you are troubleshooting authentication or deployment hooks this information is going to be critical for troubleshooting. In fact, simply looking at the logs might help you resolve the issue without having to engage the community.
Provide a Sample Repository
You should assume that drone is working correctly for most people, and therefore you'll need to provide the community with a way to repeat the issue. The easiest way to do this is to create a public, open source repository in GitHub that isolates the problem that we can use to further debug.
Verify Before Opening Issues
Please use the gitter room or the mailing list to debug issues or ask questions. Please reserve the GitHub issue tracker for confirmed, repeatable issues that you have previously discussed with the community.
Be patient and polite
Please be patient with those helping you. We understand that it can be frustrating when your build doesn't work as expected, however, remember this is a community of volunteers. Bear with us and I'm sure we'll get it figured out.
If you have a good experience working with the community and resolving an issue, please considering giving us a shoutout on Twitter. It is a simple gesture, but something we genuinely appreciate.