Closed editorialbot closed 10 months ago
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1093/bioinformatics/bty191 is OK
- 10.21105/joss.01915 is OK
- 10.1186/s13059-021-02296-0 is OK
- 10.1371/journal.pbio.3001507 is OK
- 10.1038/s41592-018-0046-7 is OK
- 10.1038/nbt.1754 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/bcm-eics, this paper is ready to be accepted and published.
Check final proof :point_right::page_facing_up: Download article
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/4935, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.
If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.
You can copy the contents for your CITATION.cff file here:
``` cff-version: "1.2.0" authors: - family-names: Kuno given-names: Akihiro orcid: "https://orcid.org/0000-0002-4674-6882" contact: - family-names: Kuno given-names: Akihiro orcid: "https://orcid.org/0000-0002-4674-6882" doi: 10.5281/zenodo.10544838 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Kuno given-names: Akihiro orcid: "https://orcid.org/0000-0002-4674-6882" date-published: 2024-01-22 doi: 10.21105/joss.06066 issn: 2475-9066 issue: 93 journal: Journal of Open Source Software publisher: name: Open Journals start: 6066 title: "cstag and cstag-cli: tools for manipulating and visualizing cs tags" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06066" volume: 9 title: "`cstag` and `cstag-cli`: tools for manipulating and visualizing cs tags" ```
If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.
🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨
Here's what you must now do:
Any issues? Notify your editorial technical team...
Everything looks fantastic! Once again, I want to extend my heartfelt thanks to all of you for the assistance in the review process!
@akikuno congratulations on this JOSS publication!
Thanks for editing @jmschrei !
And a special thank you to the reviewers: @betteridiot, @jbloom !!!!
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
If you would like to include a link to your paper from your README use the following code snippets:
Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.06066/status.svg)](https://doi.org/10.21105/joss.06066)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06066">
<img src="https://joss.theoj.org/papers/10.21105/joss.06066/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06066/status.svg
:target: https://doi.org/10.21105/joss.06066
This is how it will look in your documentation:
We need your help!
The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
Submitting author: !--author-handle-->@akikuno<!--end-author-handle-- (Akihiro Kuno) Repository: https://github.com/akikuno/cstag Branch with paper.md (empty if default branch): joss Version: 1.0.5, 1.0.0 Editor: !--editor-->@jmschrei<!--end-editor-- Reviewers: @betteridiot, @jbloom Archive: 10.5281/zenodo.10544838
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
@betteridiot & @jbloom, 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 @jmschrei 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
📝 Checklist for @betteridiot
📝 Checklist for @jbloom