Implement Phase 1 maintenance on the repo's root directory #79
Conversation
…es and title structure.
|
Will appease codacy style next week. |
| @@ -0,0 +1,4 @@ | |||
| # Code of Conduct | |||
|
|
|||
| Everyone interacting in the pyOpenSci project's codebases, issue trackers, chat rooms, and communication venues is | |||
There was a problem hiding this comment.
I've been meaning to add an organization wide COC in our .github repo -- I just made an asana task for this as it doesn't belong to a single repo rather to the organization
| 2. Update the pyOpenSci website's package listing with the package's DOI, documentation URL. | ||
| 3. Update the package's stats including stars, contributors, etc. using the GitHub API | ||
|
|
||
| ## process\_reviews.py script |
There was a problem hiding this comment.
| ## process\_reviews.py script | |
| ## process_reviews.py script |
|
|
||
| This repo contains a small module and 3 CLI scripts. | ||
| [](https://pypi.org/project/pyosmeta/) |
There was a problem hiding this comment.
@willingc should we rename the repo to be pyosmeta?
I actually forgot that i pushed this to pypi. I can also setup VCS versioning and github action based release / publish workflow . i've wanted to create that tutorial anyway so minus well do it using hatchling!
There was a problem hiding this comment.
@willingc this is a great PR. thank you. i'll open up a PR about VCS-based versioning. i thnk it will be really good for me to add that because i do it so infrequently BUT i've had to help other people set it up. i'll create the tutorial while i'm adding that functionality to this repo (as a test to ensure things work!).
lets 
:)
|
merging this - we can revisit codacy via #80 |
Addresses #78 phase 1.
This PR: