You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes in file .github/CODE_OF_CONDUCT.md:
* Style refactoring
Changes in file .github/ISSUE_TEMPLATE.md:
* Style refactoring
Changes in file .github/ISSUE_TEMPLATE/bug_report.md:
* Style refactoring
Changes in file .github/PULL_REQUEST_TEMPLATE.md:
* Minor updates
* Style refactoring
Changes in file .github/workflows/Tests.yml:
* More tweaks for GHI #365 related to coverage
* split off DOCTESTS job
* related work
Changes in file Makefile:
* related work
Changes in file tests/__init__.py:
* related work
Changes in file tests/check_integration_coverage:
* related work
Changes in file tests/test_basic.py:
* style changes
Changes in file tests/test_build.py:
* related work
Changes in file tests/test_extra.py:
* test-case regression fix
Changes in file tests/test_fuzz.py:
* edge-case regression fix
>>Please check the [list of issues](../) before creating a new one.
1
+
> Your Issue may have already been reported!
2
+
> Please check the [list of issues](../) before creating a new one.
3
3
4
4
## Basic Info
5
-
>> When reporting an issue, please list the version of Python Multicast Library you are using and any relevant information about your software environment:
6
-
- Python version:
7
-
>> `python3 --version || python --version`
8
-
- OS type
9
-
>> `uname -a`
10
-
-[ ] linux
11
-
-[ ] MacOS (darwin)
12
-
-`multicast` version:
13
-
>> `python3 -m multicast --version`
14
5
6
+
> When reporting an issue, please list the version of Python Multicast Library you are using and
7
+
> any relevant information about your software environment:
8
+
> - Python version:
9
+
>> `python3 --version || python --version`
10
+
> - OS type
11
+
>> `uname -a`
12
+
> -[ ] Linux
13
+
> -[ ] MacOS (darwin)
14
+
> -`multicast` version:
15
+
>> `python3 -m multicast --version`
15
16
17
+
## Steps to Reproduce Issue
16
18
17
-
## Steps to Reproduce Issue:
19
+
> Avoid vague language like "it doesn't work." Please describe as specifically as you can what
20
+
> behavior you are actually seeing (eg: an error message? a nil return value?).
18
21
19
-
>> Avoid vague language like "it doesn't work." Please describe as specifically as you can what behavior you are actually seeing (eg: an error message? a nil return value?).
20
22
1.
21
23
2.
22
24
3.
23
25
4.
24
26
25
-
## Logs (If Available):
26
-
>> Please attach any logs from Multicast relevant to the bug.
27
+
## Logs
28
+
29
+
*(If Available)*
30
+
31
+
> Please attach any logs from Multicast relevant to the bug.
This is the checklist that I try to go through for every single pull request that I get. If you're wondering why it takes so long for me to accept pull requests, this is why.
3
+
> Here is a basic PR template. (remove instructions and this line and above before marking ready)
4
+
5
+
# Patch Notes
6
+
7
+
## Impacted GHI
8
+
9
+
-[x] Closes _ID_
10
+
-[x] Contributes to _ID_
11
+
-[ ] Opens _ID_
12
+
13
+
14
+
## Included and Superseded PR/MRs
15
+
16
+
* Supersedes _ID_
17
+
* Includes and Supersedes _ID_
18
+
19
+
---
20
+
21
+
<details><summary>Release Instructions</summary>
22
+
23
+
# Reviewing Instructions
24
+
25
+
This is the checklist that I try to go through for every single pull request that I get.
26
+
If you're wondering why it takes so long for me to accept pull requests, this is why.
4
27
5
28
## General
6
29
7
30
-[ ] Is this change useful to me, or something that I think will benefit others greatly?
8
31
-[ ] Check for overlap with other PRs.
9
-
-[ ] Think carefully about the long-term implications of the change. How will it affect existing projects that are dependent on this? How will it affect my projects? If this is complicated, do I really want to maintain it forever? Is there any way it could be implemented as a separate package, for better modularity and flexibility?
32
+
-[ ] Think carefully about the long-term implications of the change.
33
+
How will it affect existing projects that are dependent on this?
34
+
How will it affect my projects?
35
+
If this is complicated, do I really want to maintain it forever?
36
+
Is there any way it could be implemented as a separate package,
37
+
for better modularity and flexibility?
10
38
11
39
## Check the Code
12
40
13
41
-[ ] If it does too much, ask for it to be broken up into smaller PRs.
14
42
-[ ] Does it pass `make test-style` (flake8, etc.)?
15
43
-[ ] Is it consistent?
16
-
-[ ] Review the changes carefully, line by line. Make sure you understand every single part of every line. Learn whatever you do not know yet.
17
-
-[ ] Take the time to get things right. PRs almost always require additional improvements to meet the bar for quality. Be very strict about quality. This usually takes several commits on top of the original PR.
44
+
-[ ] Review the changes carefully, line by line.
45
+
Make sure you understand every single part of every line.
46
+
Learn whatever you do not know yet.
47
+
-[ ] Take the time to get things right.
48
+
PRs almost always require additional improvements to meet the bar for quality.
49
+
Be very strict about quality. This usually takes several commits on top of the original PR.
18
50
19
51
## Check the Tests
20
52
21
53
-[ ] Does it have tests? If not:
22
54
23
-
-[ ] Comment on the PR "Can you please add tests for this code to `tests/test_blah.py`", or...
24
-
-[ ] Write the tests yourself.
55
+
-[ ] Comment on the PR "Can you please add tests for this code to `tests/test_blah.py`", or...
56
+
-[ ] Write the tests yourself.
25
57
26
-
-[ ] Do the tests pass for all of the CI tests? If not, write a note in the PR to fix CI, or fix them yourself.
58
+
-[ ] Do the tests pass for all of the CI tests? If not, write a note in the PR to fix CI,
59
+
or fix them yourself.
27
60
28
61
## Check the Docs
29
62
30
63
-[ ] Does it have docs? If not:
31
64
32
-
-[ ] Comment on the PR "Can you please add docs for this feature to the wiki", or...
33
-
-[ ] Write the docs yourself.
65
+
-[ ] Comment on the PR "Can you please add docs for this feature to the wiki", or...
66
+
-[ ] Write the docs yourself.
34
67
35
68
-[ ] If any new functions/classes are added, do they contain docstrings?
36
69
@@ -42,10 +75,14 @@ This is the checklist that I try to go through for every single pull request tha
42
75
## Close Issues
43
76
44
77
-[ ] Merge the PR branch. This will close the PR's issue.
45
-
-[ ] Close any duplicate or related issues that can now be closed. Write thoughtful comments explaining how the issues were resolved.
78
+
-[ ] Close any duplicate or related issues that can now be closed.
79
+
Write thoughtful comments explaining how the issues were resolved.
46
80
47
81
## Release (optional)
48
82
49
83
-[ ] Decide whether the changes in master make sense as a major, minor, or patch release.
50
-
-[ ] Look at the clock. If you're tired, release later when you have time to deal with release problems.
84
+
-[ ] Look at the clock. If you're tired, release later,
85
+
when you have time to deal with release problems.
51
86
-[ ] Then follow all the steps in [Release Checklist]
0 commit comments