repo PR configurations

Author: Alessandro100

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+**Summary:**
+
+Summarize the changes in the pull request including how it relates to any issues (include the #number, or link them).
+
+**Expected behavior:** 
+
+Explain and/or show screenshots for how you expect the pull request to work in your testing (in case other devices exhibit different behavior).
+
+**Testing tips:**
+
+Provide tips, procedures and sample files on how to test the feature.
+Testers are invited to follow the tips AND to try anything they deem relevant outside the bounds of the testing tips. 
+
+Please make sure these boxes are checked before submitting your pull request - thanks!
+
+- [ ] Run the unit tests with `yarn test` to make sure you didn't break anything
+- [ ] Add or update any needed documentation to the repo
+- [ ] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
+- [ ] Linked all relevant issues
+- [ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

.github/config.yml

@@ -0,0 +1,32 @@
+# Configuration for welcome - https://github.com/behaviorbot/welcome
+
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  Thanks for opening your first issue in this project! If you haven't already, you can [join our slack](https://share.mobilitydata.org/slack) and join the #mobility-database channel to meet our awesome community. Come say hi :wave:!
+  <br><br> Welcome to the community and thank you for your engagement in open source! :tada:
+  <br><br> ![](https://media.giphy.com/media/l2JHZ0dIcyFo5UQGQ/giphy.gif)
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  Thanks for opening this pull request! You're awesome.
+  We use [semantic commit messages](https://github.com/electron/electron/blob/main/docs/development/pull-requests.md#commit-message-guidelines) to streamline the release process. Before your pull request can be merged, you should **update your pull request title** to start with a semantic prefix.
+  Examples of titles with semantic prefixes:
+    - `fix: Bug with ssl network connections + Java module permissions.`
+    - `feat: Initial support for multiple @PrimaryKey annotations`.
+    - `docs: update RELEASE.md with new process`
+  To get this PR to the finish line, please do the following:
+    - Include tests when adding/changing behavior
+    - Include screenshots
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  :partying_face: Congrats on getting your first pull request merged!
+  <br><br> ![](https://media.giphy.com/media/l4KhQo2MESJkc6QbS/giphy.gif)
+
+# It is recommend to include as many gifs and emojis as possible

package.json

@@ -137,5 +137,8 @@
     "ts-node": "^10.9.2",
     "typescript": "^5.2.2",
     "wait-on": "^7.0.1"
+  },
+  "engines": {
+    "node": "24.x"
   }
 }