docs(customization): update title level

[Lee-W]

Types of changes

Please put an x in the box that applies

• Documentation Update

Description

update title level for customization documentation

from

to

Checklist:

• Add test cases to all the changes you introduce
• Run ./script/lint and ./script/test locally to ensure this change passes linter check and test
• Test the changes on the local machine manually
• Update the documentation for the changes

Steps to Test This Pull Request

None

Expected behavior

None

Related Issue

If applicable, reference to the issue related to this pull request.

Additional context

Add any other context or screenshots about the pull request here.

[codecov]

Codecov Report

Merging #207 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #207   +/-   ##
=======================================
  Coverage   95.64%   95.64%           
=======================================
  Files          34       34           
  Lines         942      942           
=======================================
  Hits          901      901           
  Misses         41       41           

Flag	Coverage Δ
#unittests	95.64% <100.00%> (ø)

Impacted Files	Coverage Δ
commitizen/__version__.py	100.00% <100.00%> (ø)

---

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 cbb9ad7...14f5de8. Read the comment docs.

[woile]

My concern with making "Customize in configuration file" the first approach we recommend is:

• How can teams reuse the designed in file configuration?
• Can cz schema, cz example, cz info be configured through file configuration?

The idea of the class approach is:

1. Publish to your pypi
2. Teams install
3. If updated -> teams update the package

[Lee-W]

How can teams reuse the designed in file configuration?

It would be a bit hard for team to reuse it. The reason why I move it to the front is because it's the easier way to config.

Can cz schema, cz example, cz info be configured through file configuration?

Yes.

e.g.,

[tool.commitizen]
...
schema = ...

The idea of the class approach is:

1. Publish to your pypi

2. Teams install

3. If updated -> teams update the package

I consider it a more advanced usage. But it also occurs to me that we can write it down more explicitly how we want user to use it.

[woile]

Agreed, this is fine as well 👍