feat(problems): add a section with the rules that must be followed when opening a new issue on GitHub

Author: quetzyg

README.md

@@ -18,6 +18,7 @@
     - [Audit Presentation](audit-presentation.md)
     - [Audit Events](audit-events.md)
 - Help
+    - [Problems?](problems.md)
     - [Troubleshooting](troubleshooting.md)
 
 ## Contributing

documentation.md

@@ -16,4 +16,5 @@
     - [Audit Presentation](/docs/{{version}}/audit-presentation)
     - [Audit Events](/docs/{{version}}/audit-events)
 - Help
+    - [Problems?](/docs/{{version}}/problems)
     - [Troubleshooting](/docs/{{version}}/troubleshooting)

faq.md

@@ -0,0 +1,16 @@
+# Having problems?
+
+If you found or have a problem with this package, let us know!
+
+Bear in mind, however, that nobody likes their time wasted, so before you rush to create a new issue on GitHub, ensure that:
+- You have **read** the [installation](installation) and [configuration](general-settings) sections of the documentation;
+- The issue you're facing is **not** documented in the [troubleshooting](troubleshooting) section;
+- A [GitHub issue](https://github.com/owen-it/laravel-auditing/issues) with the problem you're having doesn't already exist (in an open or closed state);
+
+If all of the above applies, feel free to [open a new issue](https://github.com/owen-it/laravel-auditing/issues/new).
+
+Also be aware that filling the [issue template](https://github.com/owen-it/laravel-auditing/blob/master/.github/ISSUE_TEMPLATE.md) is **mandatory** when opening a new issue.
+
+Failure to do so, will result in a closed ticket.
+
+Abide by these simple terms, and we're all good :-)