1
0
Fork 0
mirror of https://github.com/betaflight/betaflight.git synced 2025-07-23 00:05:33 +03:00

Removed markup notation for URLs from issue / request templates, since markup isn't supported in the entry field (and the template should be removed before posting).

This commit is contained in:
mikeller 2017-10-15 10:38:53 +13:00
parent 33461b99e5
commit 60e487399d
2 changed files with 3 additions and 3 deletions

View file

@ -1,11 +1,11 @@
# If your issue looks like a hardware fault or a configuration problem please don't raise an issue here.
## Please consider using other user support options such as asking the manufacturer of the hardware you are using, [RCGroups](https://rcgroups.com/forums/showthread.php?t=2464844), [Slack](https://slack.betaflight.tech) or other user support forums & groups (e.g. facebook).
## Please consider using other user support options such as asking the manufacturer of the hardware you are using, RCGroups: https://rcgroups.com/forums/showthread.php?t=2464844, or Slack: https://slack.betaflight.tech or other user support forums & groups (e.g. facebook).
## If you believe there is an issue with the firmware itself please follow these steps:
1.) Describe your problem;
2.) Include ways to reproduce the problem;
3.) Provide information about your flightcontroller and other components including how they are connected/wired;
4.) Add the used configuration and firmware version;
5.) Create a `diff` and post it here in a code block. Put \`\`\` (three backticks) at the start and end of the `diff` block ([instructions](https://oscarliang.com/use-diff-not-dump-betaflight/) on how to do a diff); and
5.) Create a `diff` and post it here in a code block. Put ``` (three backticks) at the start and end of the `diff` block (instructions on how to do a diff: https://oscarliang.com/use-diff-not-dump-betaflight/); and
6.) Remove this Text :).

View file

@ -2,7 +2,7 @@
1.) Pull requests will only be accepted if they are opened against the `master` branch. Pull requests opened against other branches without prior consent from the maintainers will be closed.
2.) Please follow the [coding style guidlines](https://github.com/cleanflight/cleanflight/blob/master/docs/development/CodingStyle.md).
2.) Please follow the coding style guidlines: https://github.com/cleanflight/cleanflight/blob/master/docs/development/CodingStyle.md.
3.) If your pull request is a fix for one or more issues that are open in GitHub, add their numbers in the form `Fixes #<issue number>`. This will cause the issues to be closed when the pull request is merged.