Skip to content

Create Issue Templates #197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rclune wants to merge 2 commits into
base: production
Choose a base branch
from
+74 −0
Open

Create Issue Templates #197

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6e498e9
Create Issue Templates
rclune Feb 3, 2026
7734cd1
Revise issue template for clarity and detail
rclune Feb 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
name: Bug report
about: Create a report to inform us of any issues that occur when using the models
in foundry.
title: "[BUG]"
labels: bug
assignees: ''

---

**Describe the bug**
A clear and concise (2-3 sentences) description of what the bug is.

**To Reproduce**
Please describe any:
- [ ] steps taken
- [ ] system architectures (if relevant)
- [ ] structure files - make a dummy structure if you cannot share your actual work
- [ ] input files - make dummy input files if you cannot share your actual work
- [ ] errors and logs, a screenshot of the pertinent parts of your error message is usually fine

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots of the output structures to help describe your problem.

**Additional context**
Add any other details that are useful for understanding the problem here.
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: "[FEAT]"
labels: enhancement
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise (2-3 sentence) description of what the problem is. Ex. I'm always have to do this post-processing step...

**Describe the solution you'd like**
A clear and concise (2-3 sentence) description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description (2-3 sentence) of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/question-or-unexpected-outputs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Question or Unexpected Outputs
about: Ask a question about how to use one of the models to accomplish your protein
design task
title: "[QUEST]"
labels: question
assignees: ''

---

** Consider asking your question on [Slack](https://join.slack.com/t/proteinmodelfoundry/shared_invite/zt-3kpwru8c6-nrmTW6LNHnSE7h16GNnfLA)! ** Your question will reach a wider audience and likely get answered faster.

**Describe the issue/question**
A clear and concise (2-3 sentences) description of what you're trying to accomplish and where you're getting stuck. Images of the expected behavior should be provided when possible.

**To Reproduce**
Please describe any:
- [ ] errors and logs, a screenshot of the pertinent parts of your error message is usually fine
- [ ] input files - make dummy input files if you cannot share your actual work
- [ ] structure files - make a dummy structure if you cannot share your actual work
- [ ] steps taken
- [ ] system architectures (if relevant)

**Additional context**
Add any other details that are useful for understanding the problem here.
Loading