@daiyam/artifact-gh-issuehub 0.1.0

package/.artifactrc.yml

@@ -0,0 +1,3 @@
+update:
+  '*':
+    update: false

package/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2025-present Baptiste Augrain
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.

package/README.md

@@ -0,0 +1,24 @@
+[@daiyam/artifact-gh-issuehub](https://github.com/daiyam/artifact-configs/tree/master/packages/gh-issuehub)
+===========================================================================================================
+
+[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
+[![NPM Version](https://img.shields.io/npm/v/@daiyam/artifact-gh-issuehub.svg?colorB=green)](https://www.npmjs.com/package/@daiyam/artifact-gh-issuehub)
+
+The configuration to use GitHub Issues as an issue tracker and accept issue report in GitHub Discussions.
+
+Getting Started
+---------------
+
+```sh
+mkdir myproject
+cd myproject
+npm init -y
+artifact add @daiyam/gh-issuehub
+```
+
+License
+-------
+
+Copyright © 2025-present Baptiste Augrain
+
+Licensed under the [MIT license](https://opensource.org/licenses/MIT).

package/configs/.github/DISCUSSION_TEMPLATE/issue-triage.yml

@@ -0,0 +1,61 @@
+labels: ["S-needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |-
+        > [!IMPORTANT]
+        > Please read through [the Discussion rules](https://github.com/REPOSITORY_SLUG/discussions/1) and check for both existing [Discussions](https://github.com/REPOSITORY_SLUG/discussions?discussions_q=) and [Issues](https://github.com/REPOSITORY_SLUG/issues?q=sort%3Areactions-desc) prior to opening a new Discussion.
+  - type: markdown
+    attributes:
+      value: "# Issue Details"
+  - type: textarea
+    attributes:
+      label: Issue Description
+      description: |-
+        Provide a detailed description of the issue. Include relevant informations.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: |-
+        Describe how you expect this project to behave in this situation. Include any relevant documentation links.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual Behavior
+      description: |-
+        Describe how this project actually behaves in this situation. If it is not immediately obvious how the actual behavior differs from the expected behavior described above, please be sure to mention the deviation specifically.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Reproduction Steps
+      description: |-
+        Provide a detailed set of step-by-step instructions for reproducing this issue.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Version
+      description: Paste the output the version here.
+      render: text
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |-
+        # User Acknowledgements
+        > [!TIP]
+        > Use these links to review the existing [Discussions](https://github.com/REPOSITORY_SLUG/discussions?discussions_q=) and [Issues](https://github.com/REPOSITORY_SLUG/issues?q=sort%3Areactions-desc).
+  - type: checkboxes
+    attributes:
+      label: "I acknowledge that:"
+      options:
+        - label: I have reviewed the FAQ and confirm that my issue is NOT among them.
+          required: true
+        - label: I have searched the repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
+          required: true
+        - label: I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (` ``` `) on separate lines.
+          required: true

package/configs/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Features, Bug Reports, Questions
+    url: https://github.com/REPOSITORY_SLUG/discussions/new/choose
+    about: Our preferred starting point if you have any questions or suggestions about configuration, features or behavior.

package/configs/.github/ISSUE_TEMPLATE/preapproved.yml

@@ -0,0 +1,26 @@
+name: Pre-Discussed and Approved Topics
+description: |-
+  Only for topics already discussed and approved in the GitHub Discussions section.
+body:
+  - type: markdown
+    attributes:
+      value: |-
+        This project doesn't accept Issues directly. Please prefer GitHub Discussions. See: https://github.com/REPOSITORY_SLUG/issues/1
+  - type: checkboxes
+    id: checkbox
+    attributes:
+      label: 'Sanity check'
+      options:
+        - label: |-
+            I read https://github.com/REPOSITORY_SLUG/issues/1
+          required: true
+  - type: textarea
+    id: body
+    attributes:
+      label: Body
+      value: |-
+        DON'T OPEN NEW ISSUES DIRECTLY, PLEASE USE THE DISCUSSIONS SECTION.
+
+        I DIDN'T READ THE ABOVE LINE. PLEASE CLOSE THIS ISSUE.
+    validations:
+      required: true

package/configs/.github/workflows/close-invalid-issue.yml

@@ -0,0 +1,28 @@
+name: Close Invalid Issue
+on:
+  issues:
+    types: [opened]
+jobs:
+  close-invalid-issue:
+    name: Close invalid issue
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+    - name: Close invalid issue
+      run: |
+        set -e # Exit if one of commands exit with non-zero exit code
+        set -u # Treat unset variables and parameters other than the special parameters '@' or '*' as an error
+        set -o pipefail # Any command failed in the pipe fails the whole pipe
+
+        BODY="$( gh issue view "${ISSUE}" --json body )"
+
+        if [[ "${BODY}" =~ "CLOSE THIS ISSUE" ]]; then
+          gh issue edit "${ISSUE}" --add-label "S-not-preapproved"
+          gh issue close "${ISSUE}" --comment "Please don't open issues directly, use GitHub Discussions instead. See: https://github.com/zokugun/REPOSITORY_SLUG/issues/1"
+          gh issue lock "${ISSUE}"
+        fi
+      env:
+        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        GH_REPO: ${{ github.repository }}
+        ISSUE: ${{ github.event.issue.number }}

package/configs/CODE_OF_CONDUCT.md

@@ -0,0 +1,91 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+**[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]**
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

package/configs/CONTRIBUTING.md

@@ -0,0 +1,114 @@
+# Contributing
+
+:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
+
+This document is intended for anyone considering opening an **issue**, **discussion** or **pull request**.
+
+> [!NOTE]
+>
+> This is a personal project that I maintain in my free time.
+> If you're expecting me to dedicate my personal time to fixing bugs, maintaining features, and reviewing code, I do kindly ask you spend a few minutes reading this document.
+> Thank you. :heart:
+
+#### Table Of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Users are not allowed to create Issues directly](#users-are-not-allowed-to-create-issues-directly)
+- [I have a bug! / Something isn't working](#i-have-a-bug--something-isnt-working)
+- [I have an idea for a feature](#i-have-an-idea-for-a-feature)
+- [I want to make changes](#i-want-to-make-changes)
+- [Spread the word](#spread-the-word)
+- [Support the project financially](#support-the-project-financially)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## Users are not allowed to create Issues directly
+
+Users are not allowed to create Issues directly in this repository - we ask that you create a [Discussion] first.
+
+This project **does not use the issue tracker for discussion or feature requests**. Instead, we use GitHub [discussions] for that. Once a discussion reaches a point where a well-understood, actionable item is identified, it is moved to the issue tracker. **This pattern makes it easier for maintainers or contributors to find issues to work on since every issue is ready to be worked on**.
+
+Any Discussion which clearly identifies a problem and can be confirmed or reproduced will be converted to an Issue by a maintainer, so as a user finding a valid problem you don't do any extra work anyway. Thank you.
+
+[Discussion]: https://github.com/REPOSITORY_SLUG/discussions
+[discussions]: https://github.com/REPOSITORY_SLUG/discussions
+
+## I have a bug! / Something isn't working
+
+First, search the issue tracker and discussions for similar issues.<br />
+Tip: also search for [closed issues] and [closed discussions] — your issue might have already been fixed!
+
+> [!NOTE]
+>
+> If there is an _open_ issue or discussion that matches your problem, **please do not comment on it unless you have valuable insight to add**.
+>
+> Use the handy upvote button for discussions, and/or emoji reactions on both discussions and issues, which are a visible yet non-disruptive way to show your support.
+
+If your issue hasn't been reported already, open an ["Issue Triage"] discussion and make sure to fill in the template **completely**. They are vital for maintainers to figure out important details about your setup.
+
+> [!WARNING]
+>
+> Please make sure that you _only_ use the "Issue Triage" category for reporting bugs — thank you!
+
+[closed issues]: https://github.com/REPOSITORY_SLUG/issues?q=is%3Aissue%20state%3Aclosed
+[closed discussions]: https://github.com/REPOSITORY_SLUG/discussions?discussions_q=is%3Aclosed
+["Issue Triage"]: https://github.com/REPOSITORY_SLUG/discussions/new?category=issue-triage
+
+## I have an idea for a feature
+
+Like bug reports, first search through both issues and discussions and try to find if your feature has already been requested. Otherwise, open a discussion in the ["Feature Requests, Ideas"] category.
+
+["Feature Requests, Ideas"]: https://github.com/REPOSITORY_SLUG/discussions/new?category=feature-requests-ideas
+
+## I want to make changes
+
+Small and trivial improvements can be submitted without any discussion.
+
+**For non-trivial changes**, pull requests should be associated with a **previously accepted issue**.<br />
+It's always better to ask for prior approval and discuss what you want to do before doing it.
+
+Discussing that you want to do something doesn't put any obligations on you. If you don't want to start the discussion just because you're afraid that you won't do it. Don't be afraid!
+
+> [!NOTE]
+>
+> **Pull requests are NOT a place to discuss feature design.** Please do not open a WIP pull request to discuss a feature. Instead, use a discussion and link to your branch.
+
+### Code hygiene
+
+When implementing features and bug fixes, please stick to the structure of the codebase as much as possible and do not take this as an opportunity to do some "refactoring along the way".
+
+Similarly:
+- **Make your changes** following our code standards
+- **Test your changes** thoroughly
+- **Update documentation** if needed
+- **Commit your changes** with clear, descriptive commit messages
+
+## Spread the word
+
+Do you like the project?
+
+* Spread the word in social networks!
+* Talk about it to your colleagues and friends
+* Write a blogpost
+* Record a YouTube video
+
+## Support the project financially
+
+Supporting the project financially counts as a contribution (even if it's just a $1/month).
+
+<table>
+    <tr>
+        <td><img src="https://raw.githubusercontent.com/daiyam/assets/master/icons/256/funding_kofi.png" alt="Ko-fi" width="80px" height="80px"></td>
+        <td><a href="https://ko-fi.com/daiyam" target="_blank">ko-fi.com/daiyam</a></td>
+    </tr>
+    <tr>
+        <td><img src="https://raw.githubusercontent.com/daiyam/assets/master/icons/256/funding_liberapay.png" alt="Liberapay" width="80px" height="80px"></td>
+        <td><a href="https://liberapay.com/daiyam/donate" target="_blank">liberapay.com/daiyam/donate</a></td>
+    </tr>
+    <tr>
+        <td><img src="https://raw.githubusercontent.com/daiyam/assets/master/icons/256/funding_paypal.png" alt="PayPal" width="80px" height="80px"></td>
+        <td><a href="https://paypal.me/daiyam99" target="_blank">paypal.me/daiyam99</a></td>
+    </tr>
+</table>

package/package.json

@@ -0,0 +1,20 @@
+{
+	"name": "@daiyam/artifact-gh-issuehub",
+	"version": "0.1.0",
+	"description": "",
+	"author": {
+		"name": "Baptiste Augrain",
+		"email": "daiyam@zokugun.org"
+	},
+	"license": "MIT",
+	"homepage": "https://github.com/daiyam/artifact-configs/tree/master/packages/gh-issuehub",
+	"repository": {
+		"type": "git",
+		"url": "https://github.com/daiyam/artifact-configs.git"
+	},
+	"bugs": {
+		"url": "https://github.com/daiyam/artifact-configs/issues"
+	},
+	"keywords": [],
+	"gitHead": "5fff6c16ace6953d55a3daee53ac9896ebf53914"
+}