Skip to content

Conversation

serengil
Copy link
Contributor

@serengil serengil commented Oct 9, 2025

Description

This PR adds GitHub issue templates to help users submit issues with a standard format.

The following templates are included:

  • Bug report – for reporting bugs in a structured way
  • Feature request – for suggesting new features
  • Documentation – for documenting improvements or corrections
  • Question – for asking questions about the project

Additionally, labels will be automatically assigned based on the selected template, helping maintain consistency and streamline issue triage.

Once, this PR is merged, then issue tracker of neo4j-graphrag-python package will be looking like this.

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Documentation update
  • Project configuration change

Complexity

Doesn't affect anything in the code base, it's all about issue tracker

Complexity:

How Has This Been Tested?

  • Unit tests
  • E2E tests
  • Manual tests

Checklist

The following requirements should have been met (depending on the changes in the branch):

  • Documentation has been updated
  • Unit tests have been updated
  • E2E tests have been updated
  • Examples have been updated
  • New files have copyright header
  • CLA (https://neo4j.com/developer/cla/) has been signed
  • CHANGELOG.md updated if appropriate

@serengil serengil requested a review from a team as a code owner October 9, 2025 13:05
@NathalieCharbel
Copy link
Contributor

Great to have this, thanks for taking it on!
Everything looks good to me, you just need to sign the CLA.
Regarding the failing e2e tests, Estelle's PR already fixes them, so you could wait for her to merge.

@serengil serengil force-pushed the feat-task-0910-issue-templates branch from bc6fb45 to 0ca924a Compare October 14, 2025 15:32
@serengil serengil merged commit 291d919 into neo4j:main Oct 14, 2025
8 checks passed
@serengil serengil deleted the feat-task-0910-issue-templates branch October 14, 2025 15: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