Fix 'campgrounds' mandatory parameters 'start-date' documentation

[acaloiaro]

Block on #91

[juftin]

Thanks for this @acaloiaro. What's the plan for the merge order/plan of these two PRs?

[acaloiaro]

Because of the _version.py dependency, I figured it would make more sense for #91 to be merged first since it would create an odd git history if a later version was merged into history before an earlier one. I'll defer to your expertise on the project here :)

---

With that said, if you'd be interested in using python-semantic-release, I'd be happy to open a PR that adds automatic versioning to the current Github Actions. That would make merge ordering moot, as the value in _version.py would be bumped in merge sequence.

One caveat with python-semantic-release is that it mandates using Angular's commit message format (https://gist.github.com/brianclements/841ea7bffdb01346392c#type), which some people understandably find onerous.

[acaloiaro]

Also @juftin -- if #91 is merged first I can rebase main onto this branch to get the documentation fix.

[juftin]

Hey @acaloiaro that plan sounds good. #91 was just merged, let's rebase and go with this.

I'll check out the Auto Version Incrementing out and consider it, it sounds useful. I'm a big fan of my existing release infra, release-drafter/release-drafter in GitHub Actions. An ideal solution in my mind would compliment that and probably use GitHub Actions to auto-increment a version based on labels (like minor, major, patch`).

[acaloiaro]

Hey @acaloiaro that plan sounds good. #91 was just merged, let's rebase and go with this.

I'll check out the Auto Version Incrementing out and consider it, it sounds useful. I'm a big fan of my existing release infra, release-drafter/release-drafter in GitHub Actions. An ideal solution in my mind would compliment that and probably use GitHub Actions to auto-increment a version based on labels (like minor, major, patch`).

---

Yeah that sounds sensible. I've always used semantic version's publish command which versions and pushes to github releases, but it also has a version command which only increments versions in code and commits the change. That might be worth looking into as a complement to release-drafter.

---

Rebase done -- everything should be good to go.

[juftin]

This looks good. Thanks for all of the improvements