docs: customize contributing guide

[heitorlessa]

Issue #, if available: #33

Description of changes:

One or two sentences as a summary of what's being changed

• Meet tenets criteria
• Update tests
• Update docs
• PR title follows conventional commit semantics

Breaking change checklist

Ignore if it's not a breaking change

RFC issue #:

• Migration process documented
• Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov-commenter]

Codecov Report

Merging #77 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop       #77   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           16        16           
  Lines          516       516           
  Branches        49        49           
=========================================
  Hits           516       516           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b9c3e6...4132ccd. Read the comment docs.

[heitorlessa]

I didn't add a CodeTour as initially planed since there will be deletion, and CodeTour needs to be pinned to a tag - I'll wait until GA.

[heitorlessa]

I removed because I created a bug report template issue that asks for more details - I’m fine putting this back to Contributing if you think is helpful. Re: PR, good point - I’ll pick one and update it

…

On Sat, 13 Jun 2020 at 09:48, Nicolas Moutschen ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In CONTRIBUTING.md <#77 (comment)> : > When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already -reported the issue. Please try to include as much information as you can. Details like these are incredibly useful: - -* A reproducible test case or series of steps Why remove this? I think this is rather helpful for us to reproduce the issue. ------------------------------ In CONTRIBUTING.md <#77 (comment)> : > 4. Commit to your fork using clear commit messages. -5. Send us a pull request, answering any default questions in the pull request interface. +5. Send us a pull request with a [conventional semantic title](https://github.com/awslabs/aws-lambda-powertools-python/pulls?q=is%3Apr+is%3Aclosed), and answering any default questions in the pull request interface. Should we have a link to what is a conventional semantic title? This links to closed PRs, which is descriptive rather than prescriptive. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBGFUYXDFOQQFSSOEGDRWM4OPANCNFSM4N4EY6QA> .

[nmoutschen]

I removed because I created a bug report template issue that asks for more details - I’m fine putting this back to Contributing if you think is helpful.

I checked the bug report template and looks good to me there, I'm fine keeping the steps out of CONTRIBUTING.md.