Skip to content

Commit

Permalink
chore: create pull request template (#126)
Browse files Browse the repository at this point in the history
  • Loading branch information
fanzhidongyzby authored Jan 25, 2025
1 parent 4b77533 commit 577675f
Showing 1 changed file with 52 additions and 0 deletions.
52 changes: 52 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
<!--
Before opening your pull request, have a quick look at our contribution guidelines:
https://github.com/TuGraph-family/OSGraph/blob/master/community/CONTRIBUTING.md
-->

## Title
<!--
And make sure that the title of your pull request follows the following format:
`<type>(<scope>): <subject>`
`<type>` is the type of your pull request.
`<scope>` is optional (including `()`) when you choose `none`.
`<subject>` is a concise sentence in lowercase.
-->

**Type**
<!-- What is the type of your pull request? Open the item by `[x]` way. -->

- [ ] `feat`: (new feature)
- [ ] `fix`: (bug fix)
- [ ] `docs`: (doc update)
- [ ] `style`: (update format)
- [ ] `refactor`: (refactor code)
- [ ] `test`: (test code)
- [ ] `chore`: (other updates)

**Scope**
<!-- Which module does your pull request mainly modify? Select `none` when undetermined. -->

- [ ] `web`: (web front-end module)
- [ ] `api`: (web api module)
- [ ] `service`: (service module)
- [ ] `data`: (graph data module)
- [ ] `search`: (search module)
- [ ] `none`: (no module)

### Description
<!-- Provide the relevant issue number associated with your pull request if needed. -->

**Issue:** #

<!-- Provide more information about this pull request. -->

### Checklist

- [ ] I have prepared the pull request title according to the requirements.
- [ ] I have successfully run all unit tests and integration tests.
- [ ] I have followed the code style guidelines of this project.
- [ ] I have already rebased the latest `master` branch.
- [ ] I have commented my code, particularly in hard-to-understand areas.
- [ ] I have made corresponding changes to the documentation.

0 comments on commit 577675f

Please sign in to comment.