[yt-svn] commit/yt: 2 new changesets

commits-noreply at bitbucket.org commits-noreply at bitbucket.org
Mon May 1 08:07:46 PDT 2017


2 new commits in yt:

https://bitbucket.org/yt_analysis/yt/commits/343f04e92ab4/
Changeset:   343f04e92ab4
Branch:      yt
User:        ngoldbaum
Date:        2017-04-27 18:03:47+00:00
Summary:     Add pull request and issue template for github
Affected #:  2 files

diff -r 27fd24ed75b89e653ddf3b1c9c76c742b51130dc -r 343f04e92ab4d2d7ae174092c849e66e069be912 .github/ISSUE_TEMPLATE.md
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,57 @@
+<!--To help us understand and resolve your issue, please fill out the form to
+the best of your ability.-->
+<!--You can feel free to delete the sections that do not apply.-->
+
+### Bug report
+
+**Bug summary**
+
+<!--A short 1-2 sentences that succinctly describes the bug-->
+
+**Code for reproduction**
+
+<!--A minimum code snippet required to reproduce the bug, also minimizing the
+number of dependencies required.-->
+
+<!-- If you need to use a data file to trigger the issue you're having, consider
+using one of the datasets from the yt data hub (http://yt-project.org/data). If
+your issue cannot be triggered using a public dataset, you can use the yt
+curldrop (https://docs.hub.yt/services.html#curldrop) to share data
+files. Please include a link to the dataset in the issue if you use the
+curldrop.-->
+
+```python
+# Paste your code here
+#
+#
+```
+
+**Actual outcome**
+
+<!--The output produced by the above code, which may be a screenshot, console
+output, etc.-->
+
+```
+# If applicable, paste the console output here
+#
+#
+```
+
+**Expected outcome**
+
+<!--A description of the expected outcome from the code snippet-->
+<!--If this used to work in an earlier version of yt, please note the
+version it used to work on-->
+
+**Version Information**
+<!--Please specify your platform and versions of the relevant libraries you are
+using:-->
+  * Operating System:
+  * Python Version:
+  * yt version:
+  * Other Libraries (if applicable): 
+
+<!--Please tell us how you installed yt and python e.g., from source,
+pip, conda. If you installed from conda, please specify which channel you used
+if not the default-->
+

diff -r 27fd24ed75b89e653ddf3b1c9c76c742b51130dc -r 343f04e92ab4d2d7ae174092c849e66e069be912 .github/PULL_REQUEST_TEMPLATE.md
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,31 @@
+<!--Thank you so much for your PR! To help us review, fill out the form
+to the best of your ability.  Please make use of the development guide at
+http://yt-project.org/docs/dev/developing/index.html-->
+
+<!--Provide a general summary of your changes in the title above, for
+example "Raises ValueError on Non-Numeric Input to set_xlim".  Please avoid
+non-descriptive titles such as "Addresses issue #8576".-->
+
+<!--If you are able to do so, please do not create the PR out of master, but out
+of a separate branch. -->
+
+## PR Summary
+
+<!--Please provide at least 1-2 sentences describing the pull request in
+detail.  Why is this change required?  What problem does it solve?-->
+
+<!--If it fixes an open issue, please link to the issue here.-->
+
+## PR Checklist
+
+<!-- Note that some of these check boxes may not apply to all pull requests -->
+
+- [ ] Code passes flake8 checker
+- [ ] New features are documented, with docstrings and narrative docs
+- [ ] Adds a test for any bugs fixed. Adds tests for new features.
+
+<!--We understand that PRs can sometimes be overwhelming, especially as the
+reviews start coming in.  Please let us know if the reviews are unclear or the
+recommended next step seems overly demanding , or if you would like help in
+addressing a reviewer's comments.  And please ping us if you've been waiting
+too long to hear back on your PR.-->


https://bitbucket.org/yt_analysis/yt/commits/f7b293c10f5a/
Changeset:   f7b293c10f5a
Branch:      yt
User:        ngoldbaum
Date:        2017-05-01 15:07:42+00:00
Summary:     Merged in ngoldbaum/yt (pull request #2593)

Add pull request and issue template for github

Approved-by: Matt Turk <matthewturk at gmail.com>
Approved-by: Kacper Kowalik <xarthisius.kk at gmail.com>
Affected #:  2 files

diff -r c8eac6c2ed9d64f40c75c56bac3568b22f7d9bce -r f7b293c10f5ab50860b0d6df59d908bda5ca8178 .github/ISSUE_TEMPLATE.md
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,57 @@
+<!--To help us understand and resolve your issue, please fill out the form to
+the best of your ability.-->
+<!--You can feel free to delete the sections that do not apply.-->
+
+### Bug report
+
+**Bug summary**
+
+<!--A short 1-2 sentences that succinctly describes the bug-->
+
+**Code for reproduction**
+
+<!--A minimum code snippet required to reproduce the bug, also minimizing the
+number of dependencies required.-->
+
+<!-- If you need to use a data file to trigger the issue you're having, consider
+using one of the datasets from the yt data hub (http://yt-project.org/data). If
+your issue cannot be triggered using a public dataset, you can use the yt
+curldrop (https://docs.hub.yt/services.html#curldrop) to share data
+files. Please include a link to the dataset in the issue if you use the
+curldrop.-->
+
+```python
+# Paste your code here
+#
+#
+```
+
+**Actual outcome**
+
+<!--The output produced by the above code, which may be a screenshot, console
+output, etc.-->
+
+```
+# If applicable, paste the console output here
+#
+#
+```
+
+**Expected outcome**
+
+<!--A description of the expected outcome from the code snippet-->
+<!--If this used to work in an earlier version of yt, please note the
+version it used to work on-->
+
+**Version Information**
+<!--Please specify your platform and versions of the relevant libraries you are
+using:-->
+  * Operating System:
+  * Python Version:
+  * yt version:
+  * Other Libraries (if applicable): 
+
+<!--Please tell us how you installed yt and python e.g., from source,
+pip, conda. If you installed from conda, please specify which channel you used
+if not the default-->
+

diff -r c8eac6c2ed9d64f40c75c56bac3568b22f7d9bce -r f7b293c10f5ab50860b0d6df59d908bda5ca8178 .github/PULL_REQUEST_TEMPLATE.md
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,31 @@
+<!--Thank you so much for your PR! To help us review, fill out the form
+to the best of your ability.  Please make use of the development guide at
+http://yt-project.org/docs/dev/developing/index.html-->
+
+<!--Provide a general summary of your changes in the title above, for
+example "Raises ValueError on Non-Numeric Input to set_xlim".  Please avoid
+non-descriptive titles such as "Addresses issue #8576".-->
+
+<!--If you are able to do so, please do not create the PR out of master, but out
+of a separate branch. -->
+
+## PR Summary
+
+<!--Please provide at least 1-2 sentences describing the pull request in
+detail.  Why is this change required?  What problem does it solve?-->
+
+<!--If it fixes an open issue, please link to the issue here.-->
+
+## PR Checklist
+
+<!-- Note that some of these check boxes may not apply to all pull requests -->
+
+- [ ] Code passes flake8 checker
+- [ ] New features are documented, with docstrings and narrative docs
+- [ ] Adds a test for any bugs fixed. Adds tests for new features.
+
+<!--We understand that PRs can sometimes be overwhelming, especially as the
+reviews start coming in.  Please let us know if the reviews are unclear or the
+recommended next step seems overly demanding , or if you would like help in
+addressing a reviewer's comments.  And please ping us if you've been waiting
+too long to hear back on your PR.-->

Repository URL: https://bitbucket.org/yt_analysis/yt/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



More information about the yt-svn mailing list