Skip to content

Commit d23fc97

Browse files
ciguaranciguaran
authored
Merge branch 'pymc-devs:main' into main
2 parents 7cdc070 + 5c600c7 commit d23fc97

File tree

373 files changed

+71629
-47565
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

373 files changed

+71629
-47565
lines changed

‎.dockerignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
.git
2+
.mypy_cache

‎.git-blame-ignore-revs

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Updated Apache v2 license header for year 2023 on entire codebase
2+
3ea470ac964f4bd5c7207ce08a583a2e6aa7ae8a

‎.gitattributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
pymc/_version.py export-subst

‎.github/ISSUE_TEMPLATE/bug-report.yml

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# This issue template was adapted from the NumPy project
2+
# under the BSD 3-Clause "New" or "Revised" License.
3+
# Copyright (c) 2005-2022, NumPy Developers.
4+
# All rights reserved.
5+
6+
name: Bug report
7+
description: Report a bug. For security vulnerabilities see Report a security vulnerability in the templates.
8+
title: "BUG: <Please write a comprehensive title after the 'BUG: ' prefix>"
9+
labels: [bug]
10+
11+
body:
12+
- type: markdown
13+
attributes:
14+
value: >
15+
Thank you for taking the time to file a bug report. Before creating a new
16+
issue, please make sure to take a few minutes to check the issue tracker
17+
for existing issues about the bug.
18+
19+
- type: textarea
20+
attributes:
21+
label: "Describe the issue:"
22+
validations:
23+
required: true
24+
25+
- type: textarea
26+
attributes:
27+
label: "Reproduceable code example:"
28+
description: >
29+
A short code example that reproduces the problem/missing feature. It
30+
should be self-contained, i.e., can be copy-pasted into the Python
31+
interpreter or run as-is via `python myproblem.py`.
32+
placeholder: |
33+
import pymc as pm
34+
<< your code here >>
35+
render: python
36+
validations:
37+
required: true
38+
39+
- type: textarea
40+
attributes:
41+
label: "Error message:"
42+
description: >
43+
Please include full error message, if any.
44+
placeholder: |
45+
<details>
46+
Full traceback starting from `Traceback: ...`
47+
</details>
48+
render: shell
49+
50+
- type: textarea
51+
attributes:
52+
label: "PyMC version information:"
53+
description: >
54+
PyMC/PyMC3 Version:
55+
PyTensor/Aesara Version:
56+
Python Version:
57+
Operating system:
58+
How did you install PyMC/PyMC3: (conda/pip)
59+
placeholder: |
60+
<details>
61+
configuration information
62+
</details>
63+
validations:
64+
required: true
65+
66+
- type: textarea
67+
attributes:
68+
label: "Context for the issue:"
69+
description: |
70+
Please explain how this issue affects your work or why it should be prioritized.
71+
placeholder: |
72+
<< your explanation here >>
73+
validations:
74+
required: false

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 0 additions & 33 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/config.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ blank_issues_enabled: false
22
contact_links:
33
- name: PyMC Discourse
44
url: https://discourse.pymc.io/
5-
about: Ask usage questions about PyMC/PyMC3
5+
about: Ask installation and usage questions about PyMC/PyMC3
66
- name: Example notebook error report
77
url: https://github.com/pymc-devs/pymc-examples/issues
88
about: Please report errors or desired extensions to the tutorials and examples here.

‎.github/ISSUE_TEMPLATE/developer.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
name: Developer issue
2+
description: This template is for developers only!
3+
4+
body:
5+
- type: textarea
6+
attributes:
7+
label: Description
8+
validations:
9+
required: true

‎.github/ISSUE_TEMPLATE/documentation.yml

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# This issue template was adapted from the NumPy project
2+
# under the BSD 3-Clause "New" or "Revised" License.
3+
# Copyright (c) 2005-2022, NumPy Developers.
4+
# All rights reserved.
5+
6+
7+
name: Documentation
8+
description: Report an issue related to the PyMC documentation.
9+
title: "DOC: <Please write a comprehensive title after the 'DOC: ' prefix>"
10+
labels: [docs]
11+
12+
body:
13+
- type: textarea
14+
attributes:
15+
label: "Issue with current documentation:"
16+
description: >
17+
Please make sure to leave a reference to the document/code you're
18+
referring to. You can also check the development version of the
19+
documentation and see if this issue has already been addressed at
20+
https://www.pymc.io/projects/docs/en/latest/api.html.
21+
22+
- type: textarea
23+
attributes:
24+
label: "Idea or request for content:"
25+
description: >
26+
Please describe as clearly as possible what topics you think are missing
27+
from the current documentation.

‎.github/ISSUE_TEMPLATE/feature-request.yml

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
# This issue template was adapted from the NumPy project
2+
# under the BSD 3-Clause "New" or "Revised" License.
3+
# Copyright (c) 2005-2022, NumPy Developers.
4+
# All rights reserved.
5+
6+
name: Feature request
7+
description: Make a specific, well-motivated proposal for a feature.
8+
title: "ENH: <Please write a comprehensive title after the 'ENH: ' prefix>"
9+
labels: [feature request]
10+
11+
12+
body:
13+
- type: markdown
14+
attributes:
15+
value: >
16+
If you're looking to request a new feature or change in functionality,
17+
including adding or changing the meaning of arguments to an existing
18+
function, please post your idea first as a [Discussion](https://github.com/pymc-devs/pymc/discussions)
19+
to validate it and bring attention to it. After validation,
20+
you can open this issue for a more technical developer discussion.
21+
Check the [Contributor Guide](https://github.com/pymc-devs/pymc/blob/main/CONTRIBUTING.md)
22+
if you need more information.
23+
24+
- type: textarea
25+
attributes:
26+
label: "Before"
27+
description: >
28+
Please fill the code snippet: How did you workaround your problem or frequent use?
29+
Leave empty if you found no workaround.
30+
render: python
31+
validations:
32+
required: false
33+
34+
- type: textarea
35+
attributes:
36+
label: "After"
37+
description: >
38+
How you see it implemented with a high level API without going into details
39+
render: python
40+
validations:
41+
required: false
42+
43+
- type: textarea
44+
attributes:
45+
label: "Context for the issue:"
46+
description: |
47+
Please explain how this issue affects your work, why it should be prioritized
48+
or add any information that did not fit Before After template.
49+
placeholder: |
50+
<< your explanation here >>
51+
validations:
52+
required: false

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 24 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,26 @@
1+
<!-- !! Thank your for opening a PR !! -->
12

2-
**Thank your for opening a PR!**
3+
**What is this PR about?**
4+
...
35

4-
Depending on what your PR does, here are a few things you might want to address in the description:
5-
+ [ ] what are the (breaking) changes that this PR makes?
6-
+ [ ] important background, or details about the implementation
7-
+ [ ] are the changes—especially new features—covered by tests and docstrings?
8-
+ [ ] [linting/style checks have been run](https://docs.pymc.io/en/latest/contributing/python_style.html)
9-
+ [ ] [consider adding/updating relevant example notebooks](https://github.com/pymc-devs/pymc-examples)
10-
+ [ ] right before it's ready to merge, mention the PR in the RELEASE-NOTES.md
6+
**Checklist**
7+
+ [ ] Explain important implementation details 👆
8+
+ [ ] Make sure that [the pre-commit linting/style checks pass](https://docs.pymc.io/en/latest/contributing/python_style.html).
9+
+ [ ] Link relevant issues (preferably in [nice commit messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html))
10+
+ [ ] Are the changes covered by tests and docstrings?
11+
+ [ ] Fill out the short summary sections 👇
12+
13+
## Major / Breaking Changes
14+
- ...
15+
16+
## New features
17+
- ...
18+
19+
## Bugfixes
20+
- ...
21+
22+
## Documentation
23+
- ...
24+
25+
## Maintenance
26+
- ...

‎.github/config.yml

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Comment to be posted to on first time issues
2+
newIssueWelcomeComment: >
3+
[![Welcome Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:8ff47a85-7250-4d86-8e48-2f346b48b2c1:BannerWelcome.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
4+
5+
:tada: Welcome to _PyMC_! :tada:
6+
We're really excited to have your input into the project! :sparkling_heart:
7+
8+
<br>If you haven't done so already, please make sure you check out our [Contributing Guidelines](https://www.pymc.io/projects/docs/en/latest/contributing/index.html) and [Code of Conduct](https://github.com/pymc-devs/pymc/blob/main/CODE_OF_CONDUCT.md).
9+
10+
11+
# Comment to be posted to on PRs from first time contributors in your repository
12+
newPRWelcomeComment: >
13+
[![Thank You Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:7fbd97cf-283b-480c-b8e1-11866e26245c:BannerThanks.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
14+
15+
:sparkling_heart: Thanks for opening this pull request! :sparkling_heart:
16+
The _PyMC_ community really appreciates your time and effort to contribute to the project.
17+
Please make sure you have read our [Contributing Guidelines](https://www.pymc.io/projects/docs/en/latest/contributing/index.html) and filled in our pull request template to the best of your ability.
18+
19+
20+
# Comment to be posted to on pull requests merged by a first time user
21+
firstPRMergeComment: >
22+
[![Congratulations Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:32fbdb89-ae1b-434e-830c-88ade86724cc:BannerCongratulations.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
23+
24+
Congrats on merging your first pull request! :tada:
25+
We here at _PyMC_ are proud of you! :sparkling_heart:
26+
Thank you so much for your contribution :gift:

‎.github/dependabot.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
version: 2
2+
updates:
3+
# Maintain dependencies for GitHub Actions
4+
- package-ecosystem: "github-actions"
5+
directory: "/"
6+
schedule:
7+
interval: "weekly"

‎.github/release.yml

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# This file contains configuration for the automatic generation of release notes in GitHub.
2+
# It's not perfect, but it makes it a little less laborious to write informative release notes.
3+
# Also see https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
4+
changelog:
5+
exclude:
6+
labels:
7+
- no releasenotes
8+
categories:
9+
- title: Major Changes 🛠
10+
labels:
11+
- major
12+
- title: New Features 🎉
13+
labels:
14+
- enhancements
15+
- feature request
16+
- title: Bugfixes 🪲
17+
labels:
18+
- bug
19+
- title: Documentation 📖
20+
labels:
21+
- docs
22+
- title: Maintenance 🔧
23+
labels:
24+
- "*"

0 commit comments

Comments
 (0)