explicit anchors (#667)

Author: maelle

approval2template.Rmd

@@ -4,20 +4,25 @@ repo-actions: true
 
 # Reviewer approval comment template {#approval2template}
 
-
 ::: {.content-hidden when-format="pdf"}
+
 ````markdown
 ```{r}
 #| results: 'asis'
 #| echo: false
 #| child: "templates/reviewer-approval.md"
 ```
 ````
+
 :::
 
 ::: {.content-visible when-format="pdf"}
+
 ```{r}
 #| child: "templates/reviewer-approval.md"
 
 ```
+
 :::
+
+

approval2template.es.Rmd

@@ -2,9 +2,10 @@
 repo-actions: true
 ---
 
-# Plantilla de comentarios de aprobación para revisión {#approval2template}
+# Plantilla de comentarios de aprobación para revisión  {#approval2template}
 
 ::: {.content-hidden when-format="pdf"}
+
 ````markdown
 ```{r}
 #| results: 'asis'
@@ -16,10 +17,12 @@ repo-actions: true
 :::
 
 ::: {.content-visible when-format="pdf"}
+
 ```{r}
 #| child: "templates/reviewer-approval.es.md"
 
 ```
+
 :::
 
 

bookreleaseissue.Rmd

@@ -4,24 +4,29 @@ repo-actions: true
 
 # Book release guidance {#bookreleaseissue}
 
-Editors preparing for a release can run the `prelease.R` script in the `inst` directory of this repository to automatically open a GitHub issue with checkpoints for all current issues assigned to the upcoming release milestone, along with the following checklist. 
+Editors preparing for a release can run the `prelease.R` script in the `inst` directory of this repository to automatically open a GitHub issue with checkpoints for all current issues assigned to the upcoming release milestone, along with the following checklist.
 Before running the script, please manually check the assignment of issues to the milestone.
 This should be run one month prior to planned release.
 
-
 ::: {.content-hidden when-format="pdf"}
+
 ````markdown
 ```{r}
 #| results: 'asis'
 #| echo: false
 #| child: "templates/book-release.md"
 ```
 ````
+
 :::
 
 ::: {.content-visible when-format="pdf"}
+
 ```{r}
 #| child: "templates/book-release.md"
 
 ```
+
 :::
+
+

bookreleaseissue.es.Rmd

@@ -2,27 +2,32 @@
 repo-actions: true
 ---
 
-# Guía para publicar el libro {#bookreleaseissue}
-
-Antes de realizar una nueva publicación de este libro, se puede ejecutar el script `prelease.R` que se encuentra en la carpeta `inst` de este repositorio. 
-Esto va a crear una *issue* en GitHub con una lista de todas las *issues* asignadas al *milestone* de la próxima versión junto con la siguiente lista de tareas. 
-Antes de correr el script, por favor revistar la asignación de *issues* al *milestone*. 
-Todo esto debería hacerse un mes antes de la fecha de publicación programada. 
+# Guía para publicar el libro  {#bookreleaseissue}
 
+Antes de realizar una nueva publicación de este libro, se puede ejecutar el script `prelease.R` que se encuentra en la carpeta `inst` de este repositorio.
+Esto va a crear una *issue* en GitHub con una lista de todas las *issues* asignadas al *milestone* de la próxima versión junto con la siguiente lista de tareas.
+Antes de correr el script, por favor revistar la asignación de *issues* al *milestone*.
+Todo esto debería hacerse un mes antes de la fecha de publicación programada.
 
 ::: {.content-hidden when-format="pdf"}
+
 ````markdown
 ```{r}
 #| results: 'asis'
 #| echo: false
 #| child: "templates/book-release.es.md"
 ```
 ````
+
 :::
 
 ::: {.content-visible when-format="pdf"}
+
 ```{r}
 #| child: "templates/book-release.es.md"
 
 ```
+
 :::
+
+

bot_cheatsheet.Rmd

@@ -1,154 +1,157 @@
-# Bot commands
+# Bot commands {#bot-commands}
 
-## For everyone {.unnumbered}
+## For everyone {#for-everyone}
 
 Note that we clean issue threads by removing extraneous content, so the record of you having asked for bot-help will most often quickly be erased or hidden.
 
-### See the list of commands available to you {.unnumbered}
+### See the list of commands available to you {#see-the-list-of-commands-available-to-you}
 
 If you need a quick reminder!
 
 ```markdown
 @ropensci-review-bot help
 ```
 
-### See the code of conduct {.unnumbered}
+### See the code of conduct {#see-the-code-of-conduct}
 
 ```markdown
 @ropensci-review-bot code of conduct
 ```
 
-## For authors {.unnumbered}
+## For authors {#for-authors}
 
-### Check package with pkgcheck {.unnumbered}
+### Check package with pkgcheck {#check-package-with-pkgcheck}
 
 When your package has substantially changed.
 
 ```markdown
 @ropensci-review-bot check package
 ```
 
-### Submit response to reviewers {.unnumbered}
+### Submit response to reviewers {#submit-response-to-reviewers}
 
 To record your response to reviewers.
 
 ```markdown
 @ropensci-review-bot submit response <response-url>
 ```
+
 where `<response_url>` is the link to the response comment in the issue thread.
 
-### Finalize repo transfer {.unnumbered}
+### Finalize repo transfer {#finalize-repo-transfer}
 
 After you've accepted the invitation to rOpenSci GitHub organization and transferred your GitHub repository to it, run this command to re-gain admin access to your repository.
 
 ```markdown
 @ropensci-review-bot finalize transfer of <package-name>
 ```
 
-### Get a new invite after approval {.unnumbered}
+### Get a new invite after approval {#get-a-new-invite-after-approval}
 
 If you missed the one-week window to accept the invitation to the rOpenSci GitHub organization, run this to receive a new one.
 
 ```markdown
 @ropensci-review-bot invite me to ropensci/<package-name>
 ```
 
-## For the editor-in-chief {.unnumbered}
+## For the editor-in-chief {#for-the-editor-in-chief}
 
-### Assign an editor {.unnumbered}
+### Assign an editor {#assign-an-editor}
 
 ```markdown
 @ropensci-review-bot assign @username as editor
 ```
 
-### Put submission on hold {.unnumbered}
+### Put submission on hold {#put-submission-on-hold}
 
 See [editorial policy](#policiesreviewprocess).
 
 ```markdown
 @ropensci-review-bot put on hold
 ```
 
-### Indicate the submission is out of scope {.unnumbered}
+### Indicate the submission is out of scope {#indicate-the-submission-is-out-of-scope}
 
 Do not forget to first post a comment explaining the decision and thanking the author(s) for their submission.
 
 ```markdown
 @ropensci-review-bot out-of-scope
 ```
 
-## For assigned editor {.unnumbered}
+## For assigned editor {#for-assigned-editor}
 
-### Put submission on hold {.unnumbered}
+### Put submission on hold {#put-submission-on-hold}
 
 See [editorial policy](#policiesreviewprocess).
 
 ```markdown
 @ropensci-review-bot put on hold
 ```
 
-### Check package with pkgcheck {.unnumbered}
+### Check package with pkgcheck {#check-package-with-pkgcheck}
 
 Generally only on pre-submission inquiries, or when authors otherwise indicate that package has substantially changed.
 
 ```markdown
 @ropensci-review-bot check package
 ```
 
-### Check statistical standards {.unnumbered}
+### Check statistical standards {#check-statistical-standards}
 
 Generally only on pre-submission inquiries, or when authors otherwise indicate that package has substantially changed.
 
 ```markdown
 @ropensci-review-bot check srr
 ```
 
-### Check that README has software review badge {.unnumbered}
+### Check that README has software review badge {#check-that-readme-has-software-review-badge}
 
 Towards the end of the submission process.
 
 ```markdown
 @ropensci-review-bot check readme
 ```
 
-### Indicate you are now seeking reviewers {.unnumbered}
+### Indicate you are now seeking reviewers {#indicate-you-are-now-seeking-reviewers}
 
 ```markdown
 @ropensci-review-bot seeking reviewers
 ```
 
-### Assign a reviewer {.unnumbered}
+### Assign a reviewer {#assign-a-reviewer}
 
 ```markdown
 @ropensci-review-bot assign @username as reviewer
 ```
 
-or 
+or
 
 ```markdown
 @ropensci-review-bot add @username as reviewer
 ```
 
-### Remove a reviewer {.unnumbered}
+### Remove a reviewer {#remove-a-reviewer}
 
 ```markdown
 @ropensci-review-bot remove @username from reviewers
 ```
 
-### Tweak review due date {.unnumbered}
+### Tweak review due date {#tweak-review-due-date}
 
 ```markdown
 @ropensci-review-bot set due date for @username to YYYY-MM-DD
 ```
 
-### Record that a review was submitted {.unnumbered}
+### Record that a review was submitted {#record-that-a-review-was-submitted}
 
 ```markdown
 @ropensci-review-bot submit review <review-url> time <time in hours>
 ```
 
-### Approve package {.unnumbered}
+### Approve package {#approve-package}
 
 ```markdown
 @ropensci-review-bot approve <package-name>
 ```
+
+