Skip to content

Commit

Permalink
Updating README to reflect current state of repo.
Browse files Browse the repository at this point in the history
  • Loading branch information
drewoldag committed Feb 26, 2024
1 parent 474ff67 commit fa5252f
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,15 @@ template can not do these for you, otherwise it would :)
- ~~In your repository settings:~~
- ~~Grant the `LSSTDESC/rail_admin` group administrator access~~
- ~~Grant the `LSSTDESC/photo-z` group maintainer access~~
- Configure Codecov for the repository
- Go here, https://github.com/apps/codecov, click the "Configure" button
- ~~Configure Codecov for the repository~~
- ~~Go here, https://github.com/apps/codecov, click the "Configure" button~~
- ~~Log in to PyPI.org and configure Trusted Publishing following these instructions https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/~~
- Create a Personal Access Token (PAT) to automatically add issues to the RAIL project tracker
- Follow these instruction to create a PAT: https://github.com/actions/add-to-project#creating-a-pat-and-adding-it-to-your-repository
- Save your new PAT as a repository secret named `ADD_TO_PROJECT_PAT`
- ~~Create a Personal Access Token (PAT) to automatically add issues to the RAIL project tracker~~
- ~~Follow these instruction to create a PAT: https://github.com/actions/add-to-project#creating-a-pat-and-adding-it-to-your-repository ~~
- ~~Save your new PAT as a repository secret named `ADD_TO_PROJECT_PAT`~~

### Before including in Rail-hub
- Make sure your `main` branch is protected
### Before including in Rail ecosystem
- ~~Make sure your `main` branch is protected~~
- Update this README
- ~~Create an example notebook~~
- ~~Run `pylint` on your code~~
Expand Down

0 comments on commit fa5252f

Please sign in to comment.