@airscript/ghitgud 1.0.0

package/.env.base

@@ -0,0 +1,2 @@
+GHITGUD_GITHUB_REPO=
+GHITGUD_GITHUB_TOKEN=

package/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @airscripts

package/.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: [airscripts]
+ko_fi: airscript

package/.github/ISSUE_TEMPLATE/build.md

@@ -0,0 +1,9 @@
+---
+name: Build
+about: Got a build system problem? Let’s fix it!
+title: ''
+labels: build
+---
+
+**What’s wrong with the build?**
+Describe the issue in the build process.

package/.github/ISSUE_TEMPLATE/chore.md

@@ -0,0 +1,9 @@
+---
+name: Chore
+about: General upkeep time!
+title: ''
+labels: chore
+---
+
+**What needs maintenance or updates?**
+Let us know what tasks should be done.

package/.github/ISSUE_TEMPLATE/ci.md

@@ -0,0 +1,9 @@
+---
+name: CI
+about: Continuous Integration to the rescue!
+title: ''
+labels: ci
+---
+
+**What needs fixing in the CI pipeline?**
+Describe what went wrong or needs improvement in CI.

package/.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,9 @@
+---
+name: Documentation
+about: Help us improve our docs!
+title: ''
+labels: documentation
+---
+
+**What’s missing from the docs?**
+Point out what needs better explanation or an update.

package/.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,9 @@
+---
+name: Feature
+about: Suggest something awesome for this project!
+title: ''
+labels: feature
+---
+
+**What amazing feature do you want to see?**
+Tell us your brilliant idea!

package/.github/ISSUE_TEMPLATE/fix.md

@@ -0,0 +1,9 @@
+---
+name: Fix
+about: Found something broken? Let's fix it!
+title: ''
+labels: fix
+---
+
+**What’s not working?**
+Describe the bug and how we can fix it.

package/.github/ISSUE_TEMPLATE/performance.md

@@ -0,0 +1,9 @@
+---
+name: Performance
+about: Speed it up!
+title: ''
+labels: performance
+---
+
+**How can we make it faster?**
+Share ideas on improving the performance.

package/.github/ISSUE_TEMPLATE/refactor.md

@@ -0,0 +1,9 @@
+---
+name: Refactor
+about: Time to clean up the code!
+title: ''
+labels: refactor
+---
+
+**What needs to be improved?**
+Let us know what part of the code can be cleaner or more efficient.

package/.github/ISSUE_TEMPLATE/style.md

@@ -0,0 +1,9 @@
+---
+name: Style
+about: Let's make it look prettier!
+title: ''
+labels: style
+---
+
+**What needs a style touch-up?**
+Tell us how we can make it look awesome.

package/.github/ISSUE_TEMPLATE/test.md

@@ -0,0 +1,9 @@
+---
+name: Tests
+about: Let’s add or fix some tests!
+title: ''
+labels: tests
+---
+
+**What needs testing?**
+Tell us what should be covered with tests.

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+# Pull Request
+
+Please fill out the details below to submit your pull request.
+
+## Label:
+
+- **Choose one label for your PR:**
+  - [ ] **Feature**
+  - [ ] **Bug**
+  - [ ] **Documentation**
+  - [ ] **Styling**
+  - [ ] **Refactor**
+  - [ ] **Performance**
+  - [ ] **Tests**
+  - [ ] **Chore**
+  - [ ] **Build**
+  - [ ] **CI**
+
+## Linked Issues:
+
+- **This PR closes the following issue(s):**
+  - Closes #<issue-number>
+  - (Add any other related issues here)
+
+## Solution:
+
+- **Describe the solution:**
+  - Briefly explain what you've done and how it addresses the issue.

package/.github/workflows/tests.yml

@@ -0,0 +1,36 @@
+name: Tests
+
+on:
+  push:
+    branches:
+      - main
+
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+
+        with:
+          node-version: 22
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+
+        with:
+          version: 10
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Run tests
+        run: pnpm run test

package/CHANGELOG.md

@@ -0,0 +1,4 @@
+# Changelog
+All notable changes to this project will be documented in this file.  
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) with some edits,
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).  

package/CITATION.cff

@@ -0,0 +1,13 @@
+cff-version: 1.2.0
+message: If you use this software in your work, please cite it using the following metadata
+title: Ghitgud
+authors:
+- family-names: Sardone
+  given-names: Francesco
+keywords:
+- credit
+- citation
+version: 1.0.0
+date-released: 2025-06-10
+license: GPL-3.0
+repository-code: https://github.com/airscripts/ghitgud

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,121 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+<francesco@airscript.it>.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by 
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,2 @@
+# Contributing
+When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository, ensuring you follow the [Code of Conduct](https://github.com/airscripts/ghitgud/blob/main/CODE_OF_CONDUCT.md).