Pin the Click version to 7.0.

[csadorf]

The recent update to Click (7.1) breaks our tests and this CI workflow,
because the help output formatting was slightly changed.

Until we have resolved other issues we should pin the Click version to
7.0.

Because of this incidence, I have added "Click" to the list of problematic dependencies.

[codecov]

Codecov Report

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

@@           Coverage Diff            @@
##           develop    #3837   +/-   ##
========================================
  Coverage    77.16%   77.16%           
========================================
  Files          458      458           
  Lines        33770    33770           
========================================
  Hits         26058    26058           
  Misses        7712     7712

Flag	Coverage Δ
#django	69.2% <ø> (ø)	⬆️
#sqlalchemy	70.02% <ø> (ø)	⬆️

---

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 8e30935...c61ef49. Read the comment docs.

[ltalirz]

Alright

[sphuber]

Just for reference @csadorf , for most PR's, especially for single commit one's we prefer to use squash-and-merge instead of a normal merge. The linear history and absence of unnecessary merge-commits makes the history easier to follow. We still use normal merges where appropriate such as the merging of feature branches. For multi commit PRs where we don't want to squash we use rebase and merge.

[csadorf]

@sphuber Thank's for letting me know. I see that these policies are documented here, however I did not originally see this, because I don't find the page name "Git style requirements" very descriptive. Maybe we can rename it or even have a separate page about "Merge policies" or so?

[sphuber]

Agreed that the current name doesn't describe its full content very well. Sounds like a more broad title or a separate page would be a good solution