"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/content/contributing/submitting-pull-requests.md" between
traefik-v2.3.2.src.tar.gz and traefik-v2.3.3.src.tar.gz

About: Traefik is a cloud native edge router, a reverse proxy and load balancer for HTTP and TCP-based applications.

submitting-pull-requests.md  (traefik-v2.3.2.src):submitting-pull-requests.md  (traefik-v2.3.3.src)
# Submitting Pull Requests # Submitting Pull Requests
A Quick Guide for Efficient Contributions A Quick Guide for Efficient Contributions
{: .subtitle } {: .subtitle }
So you've decided to improve Traefik? So you've decided to improve Traefik?
Thank You! Thank You!
Now the last step is to submit your Pull Request in a way that makes sure it get s the attention it deserves.
Let's go through the classic pitfalls to make sure everything is right. Please review the [guidelines on creating PRs](https://github.com/traefik/contri
butors-guide/blob/master/pr_guidelines.md) for Traefik in our [contributors guid
## Title e repository](https://github.com/traefik/contributors-guide).
The title must be short and descriptive. (~60 characters)
## Description
Follow the [pull request template](https://github.com/traefik/traefik/blob/maste
r/.github/PULL_REQUEST_TEMPLATE.md) as much as possible.
Explain the conditions which led you to write this PR: give us context.
The context should lead to something, an idea or a problem that you’re facing.
Remain clear and concise.
Take time to polish the format of your message so we'll enjoy reading it and wor
king on it.
Help the readers focus on what matters, and help them understand the structure o
f your message (see the [Github Markdown Syntax](https://help.github.com/article
## PR Content
- Make it small.
- One feature per Pull Request.
- Write useful descriptions and titles.
- Avoid re-formatting code that is not on the path of your PR.
- Make sure the [code builds](building-testing.md).
- Make sure [all tests pass](building-testing.md).
- Add tests.
- Address review comments in terms of additional commits (and don't amend/squash
existing ones unless the PR is trivial).
!!! note "Third-Party Dependencies"
If a PR involves changes to third-party dependencies, the commits pertaining
to the vendor folder and the manifest/lock file(s) should be committed separate
!!! tip "10 Tips for Better Pull Requests"
We enjoyed this article, maybe you will too! [10 tips for better pull reques
 End of changes. 2 change blocks. 
1 lines changed or deleted 0 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)