Kirill Müller
Kirill Müller
But then again we don't push if we don't have a remote (yet); fledge also (should) work in this case.
The release functions are named `pre_release()`, `release()` and `post_release()`, we can still rename them.
Maybe `fledge::sign_off()` ?
The diagram should document the workflow and the various commands available in fledge. Should we use mermaid?
I have a diagram that we could use or adapt: [FledgeFlow.zip](https://github.com/cynkra/fledge/files/7179837/FledgeFlow.zip)
Not needed for a quiet release.
I no longer think the demo vignette should recommend that, with #27. Let's remove the note on `use_release_issue()` and focus later on documenting fledge's release process.
I agree that adoption will be easier if we market fledge as a more or less "natural" extension of usethis workflows.
Good idea. We should definitely add `_R_CHECK_FORCE_SUGGESTS_`, let's not spend time now on the "new file" thing.
Not yet, I tend to use the standard CoC from usethis (but the wording of v2 was a bit odd last time I checked).