Skip to content

Fix/296: Added three template similar to pecan #329

Draft
ayushman1210 wants to merge 3 commits into
PecanProject:masterfrom
ayushman1210:fix/296
Draft

Fix/296: Added three template similar to pecan #329
ayushman1210 wants to merge 3 commits into
PecanProject:masterfrom
ayushman1210:fix/296

Conversation

@ayushman1210
Copy link
Copy Markdown
Contributor

@ayushman1210 ayushman1210 commented Apr 27, 2026

Under the .github/Issue_Template/ directory
I have added three files

  1. Bug_report.md
  2. Feature_request.md
  3. Doc_changes.md

I fetched the templates that the pecan project uses and created them

FIX:#296

@ayushman1210
Copy link
Copy Markdown
Contributor Author

hey @Alomir please review this one when you have some free time
thanks !!

Copy link
Copy Markdown
Collaborator

@Alomir Alomir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great start, I have some proposed tweaks. Please feel free to wordsmith my suggestions!

## Use Cases and Requirements

**Describe the use cases and requirements**
Please focus on describing the problem and your requirements without going into the solution space. We believe in understanding requirements before design, and design before solution!
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love this, but it might be a little too preachy 😂

How about:
Please focus on describing the problem and your requirements without going into the solution space; this will help us design the best solution for this request.

Comment on lines +9 to +10
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be careful not to make this seem like a bug report. How about something like:

** A short summary of your requested feature**
Please describe the problem you are trying to solve, or the functionality you would like to see added.

Comment on lines +17 to +20
## Alternatives Considered (Optional)

**Describe alternatives you've considered**
A clear and concise description of any alternative workflows or workarounds you are currently using.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section should be dropped? This is solution space stuff.

Comment on lines +15 to +19
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is pretty gui-centric, which is often good but not here. Perhaps:

Include all relevant information to reproduce the error, if possible, including:

  1. sipnet command run, with all command line options
  2. input files used that show the problem
  3. output files from the above

@Alomir
Copy link
Copy Markdown
Collaborator

Alomir commented May 12, 2026

Moving this to draft for now. Please move it back when it's ready!

@Alomir Alomir marked this pull request as draft May 12, 2026 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants