GitHub pages always deploys latest version

[tomjemmett]

The pkgdown action always deploys latest version of master branch, but this will often not reflect what is deployed to cran.

Options:

1. we should only deploy when a new tag is generated (for a release),
2. we should indicate clearly that this is the latest version available on GitHub, not all features will be in the cran release,
3. we should start using a development branch, we only push changes to master when we are ready to submit to cran

Option 2 would get my vote as it's the easiest to implement and most pragmatic.

[chrismainey]

This depends on whether we want to use a 'proper' branching structure e.g. GitFlow with a development branch that only merges to main for a release (like 3), or whether we use the 'working' version number that works with pkgdown, with 9999 on the end. You can turn it off with that then. Would mean that I deploy to cran on release, then immediately commit a ..9999 version to put repo in 'development.'

[tomjemmett]

I would probably vote for latter rather than gitflow, that feels a little too over the top for this project

[chrismainey]

OK, will release via CRAN then switch repo to development mode, and make sure it's explicit on the README.