dpl v2 gh-pages documentation fails to provide default values for many of the options

[JasonGross]

On https://docs.travis-ci.com/user/deployment-v2/providers/pages/#known-options , there is no default mentioned for allow_empty_commit, verbose, committer_from_gh, and others.

The v1 docs here have defaults for many of these options:

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[JasonGross]

This issue is not stale, as can be easily determined by visiting the link in the report.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[JasonGross]

This issue is still open, as is obvious from 10 seconds of inspection. Why has there been no response from the team for six months on this very simple issue?

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[JasonGross]

It's been almost two years and the only response I've gotten to this issue is from @Stale[bot]