Skip to content

some tweaks to contrib and templates #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 30, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/ISSUE_TEMPLATE/tracker.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,8 @@ labels: tracker id
File:
Reviewers:

## Context
> The sections below may still be pending. If so, the issue is still available, it simply doesn't
> have specific guidance yet. Please refer to [this overview of updates](https://github.com/pymc-devs/pymc-examples/wiki/Notebook-updates-overview)

## Known changes needed
Changes listed in this section should all be done at some point in order to get this
Expand All @@ -35,4 +36,4 @@ the notebook but may not have a clear implementation, or fix some know issue onl

### Exotic dependencies

### Computing power
### Computing requirements
8 changes: 8 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,14 @@ Before starting a work on a pull request look at the tracker issue of the
notebook you are planning to edit to make sure it is not being updated by someone
else.

**Note on labels**: The labels on an issue will apply to the most immediate 1 position update.
One issue can be labeled "good first issue" for updating from "To Do" to "General updates", but
that does not mean that updating from "To Do"->"ArviZ" or
"General Updates"->"Best Practices" won't be challenging.
The same could be true the other way around.
In case of doubt, don't hesitate to ask and read over the notebook to
see what changes are expected.

If there are no comments and nobody is working on this notebook,
comment on the ticket to make it evident to others, we will assign
the issue to you as soon as possible.
Expand Down