roboneuro
commented
3 weeks ago Hello @agahkarakuzu, here are the things you can ask me to do:
# List all available commands
@roboneuro commands
# Add to this issue's reviewers list
@roboneuro add @username as reviewer
# Remove from this issue's reviewers list
@roboneuro remove @username from reviewers
# Get a list of all editors's GitHub handles
@roboneuro list editors
# Assign a user as the editor of this submission
@roboneuro assign @username as editor
# Remove the editor assigned to this submission
@roboneuro remove editor
# Remind an author, a reviewer or the editor to return to a review after a
# certain period of time (supported units days and weeks)
@roboneuro remind @reviewer in 2 weeks
# Check the references of the PDF for missing DOIs
@roboneuro check references
# Perform checks on the repository
@roboneuro check repository
# Adds a checklist for the reviewer using this command
@roboneuro generate my checklist
# Set a value for version
@roboneuro set v1.0.0 as version
# Set a value for branch
@roboneuro set neurolibre-paper as branch
# Set a value for repository
@roboneuro set https://github.com/organization/repo as repository
# Set a value for the archive DOI
@roboneuro set set 10.5281/zenodo.6861996 as archive
# Set a value for the (data/book/repository/docker) archive DOI.
@roboneuro set 10.5281/zenodo.6861996 as data archive
# Set executable book URI for the preprint.
@roboneuro set book uri
# Mention the EiCs for the correct track
@roboneuro ping track-eic
# Reject paper
@roboneuro reject
# Withdraw paper
@roboneuro withdraw
# Invite an editor to edit a submission (sending them an email)
@roboneuro invite @(.*) as editor
# Builds myst article. First argument is the commit hash, second is the binder hash.
@roboneuro build (\S+) myst at runtime (\S+)
# Generates the pdf paper
@roboneuro generate pdf
# Recommends the submission for acceptance
@roboneuro recommend-accept
# Accept and publish the paper
@roboneuro accept
# Update data on an accepted/published paper
@roboneuro reaccept
# Generates a LaTeX preprint file
@roboneuro generate preprint
# Flag submission with questionable scope
@roboneuro query scope
# Get a link to the complete list of reviewers
@roboneuro list reviewers
# Creates a post-review checklist with editor and authors tasks
@roboneuro create post-review checklist
# Open the review issue
@roboneuro start review
# Check the status of the NeuroLibre preview server.
@roboneuro preview server status
# Check the status of the NeuroLibre preprint (production) server.
@roboneuro preprint server status
# Build a NeuroLibre reproducible preprint for technical screening.
@roboneuro build book
# After screening, build book from the forked reository.
@roboneuro production build book
# Transfer data from preview to the preprint (production) server.
@roboneuro production sync data
# Transfer the final preprint (forked repo) to the preprint (production) server (DOI URL).
@roboneuro production sync book
# Start the production process by forking repository and configuring it.
@roboneuro production start
# Creates Zenodo deposits (a.k.a buckets) for archiving reproducibility assets.
@roboneuro zenodo create buckets
# Status check for the archival of the reproducibility assets.
@roboneuro zenodo status
# Copy summary PDF from the preprints repository to the NeuroLibre production server.
@roboneuro production sync pdf
# Upload the latest Jupyter Book to Zenodo for archival.
@roboneuro zenodo upload book
# Upload the latest version of the book repository to Zenodo for archival.
@roboneuro zenodo upload repository
# Upload the latest version of the docker image to Zenodo for archival.
@roboneuro zenodo upload docker
# Upload the submission data to Zenodo for archival. Will not take effect if the data is already archived.
@roboneuro zenodo upload data
# DESTRUCTIVE ACTION: Deletes zenodo records and all the data that has been uploaded. Cannot perform after zenodo publish.
@roboneuro zenodo flush
# Publish reproducibility assets on Zenodo. Sets DOIs if successful.
@roboneuro zenodo publish
# Build an extended PDF for the target repository.
@roboneuro build extended pdf
# Download the submission data.
@roboneuro cache data
agahkarakuzu
Submitting author: !--author-handle-->@arcj-hub<!--end-author-handle-- (Jessica Archibald) Repository: https://github.com/arcj-hub/MRShiny-Brain Branch with paper.md (empty if default branch): Version: 4.3.2 (Rversion) Editor: !--editor-->@agahkarakuzu<!--end-editor-- Reviewers: !--reviewers-list-->@agahkarakuzu<!--end-reviewers-list-- Reproducible preprint: Pending Repository archive: Pending Data archive: N/A Book archive: Pending Docker archive: N/A
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@agahkarakuzu, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @agahkarakuzu know.
✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨
Checklists
@agahkarakuzu, please create your checklist typing:
@roboneuro generate my checklist