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
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/question.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
name: Question
3
3
about: How do I... I need help with...
4
-
title: "[HELP]"
4
+
title: "help:"
5
5
labels: ''
6
6
assignees: ''
7
7
@@ -18,8 +18,8 @@ But if you are just asking a question:
18
18
* Am I doing something wrong?
19
19
* I can't build OpenImageIO
20
20
21
-
For anything of this nature, the best way to get help using OpenImageIO is
22
-
to ask a question on the [oiio-dev developer mail list](https://lists.aswf.io/g/oiio-dev).
21
+
For anything of this nature, the best way to get help using OpenImageIO is to
22
+
ask a question on the [oiio-dev developer mail list](https://lists.aswf.io/g/oiio-dev) or the [ASWF Slack](https://slack.aswf.io)`#openimageio` channel.
23
23
24
24
The [documentation](https://docs.openimageio.org)
25
25
is pretty comprehensive, so please check there first; you may find the answer
<!-- This is just a guideline and set of reminders about what constitutes -->
2
-
<!-- a good PR. Feel free to delete all this matter and replace it with -->
3
-
<!-- your own detailed message about the PR, assuming you hit all the -->
4
-
<!-- important points made below. -->
1
+
YOU MAY DELETE ALL OF THIS IF YOU ALREADY HAVE A DESCRIPTIVE COMMIT MESSAGE!
5
2
3
+
This is just a template and set of reminders about what constitutes a good PR.
4
+
But please look over the checklist at the bottom.
6
5
7
-
## Description
6
+
If THIS TEXT is still in your PR description, we'll know you didn't read the
7
+
instructions!
8
+
9
+
10
+
11
+
12
+
### Description
8
13
9
14
<!-- Please provide a description of what this PR is meant to fix, and -->
10
15
<!-- how it works (if it's not going to be very clear from the code). -->
11
16
12
-
## Tests
17
+
###Tests
13
18
14
19
<!-- Did you / should you add a testsuite case (new test, or add to an -->
15
20
<!-- existing test) to verify that this works? -->
16
21
17
22
18
-
## Checklist:
23
+
###Checklist:
19
24
20
25
<!-- Put an 'x' in the boxes as you complete the checklist items -->
21
26
22
-
-[ ] I have read the [contribution guidelines](https://github.com/AcademySoftwareFoundation/OpenImageIO/blob/main/CONTRIBUTING.md).
23
-
-[ ] I have updated the documentation, if applicable. (Check if there is no
24
-
need to update the documentation, for example if this is a bug fix that
25
-
doesn't change the API.)
26
-
-[ ] I have ensured that the change is tested somewhere in the testsuite
27
-
(adding new test cases if necessary).
28
-
-[ ] If I added or modified a C++ API call, I have also amended the
29
-
corresponding Python bindings (and if altering ImageBufAlgo functions, also
30
-
exposed the new functionality as oiiotool options).
31
-
-[ ] My code follows the prevailing code style of this project. If I haven't
32
-
already run clang-format before submitting, I definitely will look at the CI
33
-
test that runs clang-format and fix anything that it highlights as being
34
-
nonconforming.
27
+
-[ ]**I have read the guidelines** on [contributions](https://github.com/AcademySoftwareFoundation/OpenImageIO/blob/main/CONTRIBUTING.md) and [code review procedures](https://github.com/AcademySoftwareFoundation/OpenImageIO/blob/main/docs/dev/CodeReview.md).
28
+
-[ ]**I have updated the documentation** if my PR adds features or changes
29
+
behavior.
30
+
-[ ]**I am sure that this PR's changes are tested somewhere in the
31
+
testsuite**.
32
+
-[ ]**I have run and passed the testsuite in CI***before* submitting the
33
+
PR, by pushing the changes to my fork and seeing that the automated CI
34
+
passed there. (Exceptions: If most tests pass and you can't figure out why
35
+
the remaining ones fail, it's ok to submit the PR and ask for help. Or if
36
+
any failures seem entirely unrelated to your change; sometimes things break
37
+
on the GitHub runners.)
38
+
-[ ]**My code follows the prevailing code style of this project** and I
39
+
fixed any problems reported by the clang-format CI test.
40
+
-[ ] If I added or modified a public C++ API call, I have also amended the
41
+
corresponding Python bindings. If altering ImageBufAlgo functions, I also
42
+
exposed the new functionality as oiiotool options.
0 commit comments