https://github.com/banesullivan/software-peer-review
pyOpenSci's guidebook for package authors, reviewers, and editors
Science Score: 23.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
○codemeta.json file
-
○.zenodo.json file
-
✓DOI references
Found 3 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (15.4%) to scientific vocabulary
Last synced: 10 months ago
·
JSON representation
Repository
pyOpenSci's guidebook for package authors, reviewers, and editors
Basic Info
- Host: GitHub
- Owner: banesullivan
- License: other
- Language: CSS
- Default Branch: main
- Homepage: https://www.pyopensci.org/software-peer-review/
- Size: 24.5 MB
Statistics
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
- Releases: 0
Fork of pyOpenSci/software-peer-review
Created over 1 year ago
· Last pushed 11 months ago
https://github.com/banesullivan/software-peer-review/blob/main/
#pyOpenSci Peer Review Guide [](#contributors-)  [](https://doi.org/10.5281/zenodo.7101777)  [](https://app.circleci.com/pipelines/github/pyOpenSci/software-peer-review) https://www.pyopensci.org/peer-review-guide/ pyOpenSci's guide for developing, reviewing, and maintaining packages. ## Contributing to this guide We welcome issues and pull requests to improve the content of this guide. If you'd like to see an improvement, please [open an issue](https://github.com/pyOpenSci/peer-review-guide/issues/). To submit a Pull Request with changes: 1. Create a fork of this repo to make changes. 2. After making changes, build the book locally from your fork to preview the changes to make sure they appear as expected (see [How to build the guide locally](https://github.com/pyopensci/peer-review-guide/#how-to-build-the-guide-locally) below) 3. When satisfied, push the changes back to GitHub and open a pull request from your fork to the main branch of this repo. 4. The Continuous Integration processes will build the book and let you and the PR reviewer(s) preview it in your browser (see [Automated build and publishing](https://github.com/pyopensci/peer-review-guide/#automated-build-and-publishing) below). 5. The reviewer of the PR may request modifications. 6. Once satisfied, the reviewer will merge your pull request! Thanks for your contribution! ## How to build the guide locally The pyOpenSci guidebook is written using [Jupyter Book](https://github.com/executablebooks/jupyter-book). To build the guide locally, take the following steps: * Clone this repository (or clone your fork by replacing "pyOpenSci" with your GitHub username): ``` git clone https://github.com/pyOpenSci/peer-review-guide ``` To build, follow these steps: 1. Install `nox` ```console pip install nox ``` 2. Build the documentation: ```console nox -s docs ``` This should create a local environment in a `.nox` folder, build the documentation (as specified in the `noxfile.py` configuration), and the output will be in `_build/html`. To build live documentation that updates when you update local files, run the following command: ```console $ nox -s docs-live ``` * To view your built book: Navigate to _build/html/ on your local clone of the repo and open "index.html". ## Automated build and publishing Whenever a pull request is opened or changes are pushed to any branch of the base repository, the book is built (separately) by both GitHub Actions and CircleCI. ### Why both GitHub Actions and CircleCI? - GitHub Actions is the main build tool. In addition to building whenever a pull request is opened from a fork, it handles publishing the book when changes are made to the main branch (e.g. once the pull request is merged). When that happens, it pushes the built html files to the gh-pages branch, which publishes the book to the [website](https://pyopensci.org/peer-review-guide/). - CircleCI's build is redundant, but it offers an easier way of viewing the built html in browser WITHOUT merging the changes to main or downloading files. See [How do you preview the the guide from a Pull Request](https://github.com/pyopensci/peer-review-guide/#how-do-you-preview-the-guide-from-a-pull-request) below for details. ### How do you preview the guide from a Pull Request? - *(Recommended)* Via the artifact redirector workflow: When viewing the checks in a pull request, click "Details" next to the "Click to preview rendered book" to be automatically taken to the CircleCI index.html preview. This is performed using the [circleci-artifacts-redirector-action workflow](https://github.com/larsoner/circleci-artifacts-redirector-action). See the gif below for a demonstration. - Via CircleCI: Go to the CircleCI job and select the "Artifacts" tab. Click on "index.html" to preview the built book. - Via GitHub Actions alone: GitHub Actions also saves the built html files for preview, but you have to download and unzip the files to your local computer. Go to your deploy-book build in the [Actions tab](https://github.com/pyOpenSci/peer-review-guide/actions). Then select "book-html" in the "Artifacts" pane near the bottom of the page. After downloading, unzip the book-html.zip file into a separate directory and open "index.html" from the directory with the unzipped files. The book should open in your web browser.  ## Contributors Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
Owner
- Name: Bane Sullivan
- Login: banesullivan
- Kind: user
- Location: United States
- Website: banesullivan.com
- Repositories: 75
- Profile: https://github.com/banesullivan
visualization geek & software engineer. co-created @pyvista.
GitHub Events
Total
- Delete event: 1
- Push event: 2
- Create event: 1
Last Year
- Delete event: 1
- Push event: 2
- Create event: 1