docs: add pull request template

[praaatap]

Description

Added a comprehensive Pull Request template (.github/pull_request_template.md) to standardise PR submissions and ensure contributors follow community guidelines.
The template includes:

• A concise description section.
• Options to specify the type of change.
• A comprehensive checklist based on existing CONTRIBUTING.md files within the precice repositories.
• A prompt for running system regression tests for non-trivial PRs.

Fixes # N/A

Type of change

• New feature or content (non-breaking change which adds functionality/content)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code/content follows the style guidelines of this project
• I have performed a self-review of my own code/content
• I have commented my code/content, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have read the contributing to preCICE page.

[MakisH]

Good point, we need something. But it should be as short as possible (regular contributors often complain about such checklists), and this currently includes a few points that don't apply.

What is mainly missing and would be very helpful here would be a declaration of AI tools used. I would like to make sure that a human is always in control of the work contributed.

Any suggestions in this direction?

[MakisH]

Since checklists show up as things to do, I would not use a checklist here. It also does not really help, a maintainer would add labels accordingly.

Let's rather remove:

Suggested change

	## Type of change
	<!-- Please delete options that are not relevant. -->
	- [ ] Bug fix (non-breaking change which fixes an issue)
	- [ ] New feature or content (non-breaking change which adds functionality/content)
	- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
	- [ ] This change requires a documentation update

[MakisH]

This is rather unclear, as we don't have such clear guidelines in this repo.

Suggested change

- [ ] My code/content follows the style guidelines of this project

[MakisH]

This is pretty much the documentation itself, I don't think this point needs to be explicit.

Suggested change

- [ ] I have made corresponding changes to the documentation

[MakisH]

A bit vague. Given that the website includes both content and technicalities, more useful would be a list of common checks for technical contributions. Not sure what these would be, though, and I would only include the absolutely necessary ones.

[praaatap]

Thanks a lot for the feedback ,@MakisH

• I have updated the PR to incorporate all the points:

• Removed the long and unclear checklists and the type of change section

• Kept the template minimal and to the point

• Added a clear declaration of AI usage to ensure transparency and human responsibility

• Aligned the text with the contribution documentation

[MakisH]

Thanks! There are a few points here that need further discussion, I will come back to you.

[praaatap]

Thank you again for your review, @MakisH.
I’d be glad to discuss the remaining points.
Please let me know which specific aspects you would like to revisit — I’m happy to refine or simplify the template accordingly

[hanzalahwaheed]

do we absolutely need to mention the names of the AI tools here?

[hanzalahwaheed]

lets add a Screenshot section as an optional section for any UI related changes. It can also include Before and After comparison views maybe.

[hanzalahwaheed]

@praaatap hey! I added some comments. Hope they help make this PR even better!