Skip to content

Commit 5ae7d18

Browse files
authored
some tweaks to contrib and templates (#59)
* some tweaks to contrib and templates * update contrib and issue template, link to wiki
1 parent e4f9afd commit 5ae7d18

File tree

2 files changed

+11
-2
lines changed

2 files changed

+11
-2
lines changed

.github/ISSUE_TEMPLATE/tracker.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ labels: tracker id
88
File:
99
Reviewers:
1010

11-
## Context
11+
> The sections below may still be pending. If so, the issue is still available, it simply doesn't
12+
> have specific guidance yet. Please refer to [this overview of updates](https://github.com/pymc-devs/pymc-examples/wiki/Notebook-updates-overview)
1213
1314
## Known changes needed
1415
Changes listed in this section should all be done at some point in order to get this
@@ -35,4 +36,4 @@ the notebook but may not have a clear implementation, or fix some know issue onl
3536

3637
### Exotic dependencies
3738

38-
### Computing power
39+
### Computing requirements

CONTRIBUTING.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,14 @@ Before starting a work on a pull request look at the tracker issue of the
3636
notebook you are planning to edit to make sure it is not being updated by someone
3737
else.
3838

39+
**Note on labels**: The labels on an issue will apply to the most immediate 1 position update.
40+
One issue can be labeled "good first issue" for updating from "To Do" to "General updates", but
41+
that does not mean that updating from "To Do"->"ArviZ" or
42+
"General Updates"->"Best Practices" won't be challenging.
43+
The same could be true the other way around.
44+
In case of doubt, don't hesitate to ask and read over the notebook to
45+
see what changes are expected.
46+
3947
If there are no comments and nobody is working on this notebook,
4048
comment on the ticket to make it evident to others, we will assign
4149
the issue to you as soon as possible.

0 commit comments

Comments
 (0)