From 2858e910dcbc0a92a2d886b8e85256d919ee1872 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Sun, 11 Dec 2022 22:20:49 +0100 Subject: [PATCH 01/35] Create LICENSE.md --- LICENSE.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 LICENSE.md diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 0000000..959d8ec --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2022 Leifer Mendez + +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. From 5303dd7d257da8b8062df732edfac0960b83caa6 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Mon, 12 Dec 2022 00:44:58 +0100 Subject: [PATCH 02/35] Create FUNDING.yml --- .github/FUNDING.yml | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 .github/FUNDING.yml diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml new file mode 100644 index 0000000..1fde58c --- /dev/null +++ b/.github/FUNDING.yml @@ -0,0 +1,2 @@ +patreon: leifermendez +custom: "https://www.buymeacoffee.com/leifermendez" From ec32dc429f005940becd3e4c279691188ed7a157 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Mon, 12 Dec 2022 16:42:12 +0100 Subject: [PATCH 03/35] Create CODE_OF_CONDUCT.md --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..05743b3 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# 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, 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 +leifer.contacto@gmail.com. +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. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From c2a6c6872d8657df467fe3c1abb601e1aaf05278 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 07:59:13 +0100 Subject: [PATCH 04/35] Create PULL_REQUEST_TEMPLATE.md --- .github/PULL_REQUEST_TEMPLATE.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .github/PULL_REQUEST_TEMPLATE.md diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..b0feb3a --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,23 @@ +# Cual version del BOT es? + +- [ ] v2 +- [ ] v1 + + +# Que tipo de ISSUE es? + +- [ ] Mejoras +- [ ] Bug +- [ ] Docs / tests + +# Description + +Por favor agrega una descripción de tu problema para tener más contexto y poder ayudar más rápido. Si es de ayuda puedes usar plataformar como [https://www.loom.com/](https://www.loom.com/) para grabar un video. + + +> Forma parte de este proyecto. + +- [Discord](https://link.codigoencasa.com/DISCORD) +- [Twitter](https://twitter.com/leifermendez) +- [Youtube](https://www.youtube.com/watch?v=5lEMCeWEJ8o&list=PL_WGMLcL4jzWPhdhcUyhbFU6bC0oJd2BR) +- [Telegram](https://t.me/leifermendez) From a43444bb3e92956132caadf69ddba3edec6a5596 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 08:02:08 +0100 Subject: [PATCH 05/35] Create bug.yml --- .github/ISSUE_TEMPLATE/bug.yml | 66 ++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug.yml diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml new file mode 100644 index 0000000..a48f175 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug.yml @@ -0,0 +1,66 @@ +name: 🐞 Bug Report +description: Something does not work or is flaky! let us know! +labels: [bug, triage] +title: '[🐞]' +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this bug report! + + - type: dropdown + id: component + attributes: + label: Which component is affected? + options: + - Qwik Runtime + - Qwik Rollup / Vite plugin + - Qwik Optimizer (rust) + - Qwik React + - Qwik City (routing) + - Starters / CLI + validations: + required: true + + - type: textarea + id: description + attributes: + description: 'A clear and concise description of what you expected to happen instead. If you intend to submit a PR for this issue, tell us in the description. Thanks!' + label: Describe the bug + placeholder: I am doing ... What I expect is ... What actually happening is ... + + validations: + required: true + + - type: input + id: reproduction + attributes: + label: Reproduction + description: Please provide a link via [qwik.new](https://qwik.new/) or a link to a repo that can reproduce the problem you ran into. `npm create qwik@latest` can be used as a starter template. A [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) is required ([Why?](https://antfu.me/posts/why-reproductions-are-required)). If a report is vague (e.g. just a generic error message) and has no reproduction, it will receive a "need reproduction" label. If no reproduction is provided after 3 days, it will be auto-closed. + placeholder: Reproduction URL + validations: + required: true + + - type: textarea + id: reproduction-steps + attributes: + label: Steps to reproduce + description: Please provide any reproduction steps that may need to be described. E.g. if it happens only when running the dev or build script make sure it's clear which one to use. + placeholder: Run `npm install` followed by `npm run dev` + + - type: textarea + id: system-info + attributes: + label: System Info + description: Output of `npx envinfo --system --npmPackages '{vite,@builder.io/*}' --binaries --browsers` + render: shell + placeholder: System, Binaries, Browsers + validations: + required: true + + - type: textarea + id: additional_information + attributes: + label: Additional Information + validations: + required: false From 851052b3d2f20742c449baa14418d02d84145696 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 10:12:21 +0100 Subject: [PATCH 06/35] Update bug.yml --- .github/ISSUE_TEMPLATE/bug.yml | 51 +++++++++++----------------------- 1 file changed, 16 insertions(+), 35 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml index a48f175..098e9da 100644 --- a/.github/ISSUE_TEMPLATE/bug.yml +++ b/.github/ISSUE_TEMPLATE/bug.yml @@ -1,33 +1,31 @@ -name: 🐞 Bug Report -description: Something does not work or is flaky! let us know! +name: 🐛 Reporte Bug +description: Algo no va bien?. Hazlo saber labels: [bug, triage] -title: '[🐞]' +title: '[🐛]' body: - type: markdown attributes: value: | - Thanks for taking the time to fill out this bug report! + Gracias por tomarte el tiempo de reportar este problema - type: dropdown id: component attributes: - label: Which component is affected? + label: ¿Sobre que afecta? options: - - Qwik Runtime - - Qwik Rollup / Vite plugin - - Qwik Optimizer (rust) - - Qwik React - - Qwik City (routing) - - Starters / CLI + - Flujo de palabras (Flow) + - DialogFlow + - Base de datos + - Otro validations: required: true - type: textarea id: description attributes: - description: 'A clear and concise description of what you expected to happen instead. If you intend to submit a PR for this issue, tell us in the description. Thanks!' - label: Describe the bug - placeholder: I am doing ... What I expect is ... What actually happening is ... + description: 'Trata de ser lo más claro posible, de esa manera podemos entender el contexto de tu problema y darte una mejor solución' + label: Describe tu problema + placeholder: Yo tengo un problema.... validations: required: true @@ -35,32 +33,15 @@ body: - type: input id: reproduction attributes: - label: Reproduction - description: Please provide a link via [qwik.new](https://qwik.new/) or a link to a repo that can reproduce the problem you ran into. `npm create qwik@latest` can be used as a starter template. A [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) is required ([Why?](https://antfu.me/posts/why-reproductions-are-required)). If a report is vague (e.g. just a generic error message) and has no reproduction, it will receive a "need reproduction" label. If no reproduction is provided after 3 days, it will be auto-closed. + label: Reproducir error + description: __(Recomendación)__ trata de grabar un video puedes usar algunas de las siguientes herramientas [https://www.vidyard.com/](https://www.vidyard.com/) [https://www.loom.com/](https://www.loom.com/) y en lo posbile apoyate en [https://stackblitz.com/](https://stackblitz.com/) para compartir el código de ser necesario placeholder: Reproduction URL validations: - required: true - - - type: textarea - id: reproduction-steps - attributes: - label: Steps to reproduce - description: Please provide any reproduction steps that may need to be described. E.g. if it happens only when running the dev or build script make sure it's clear which one to use. - placeholder: Run `npm install` followed by `npm run dev` - - - type: textarea - id: system-info - attributes: - label: System Info - description: Output of `npx envinfo --system --npmPackages '{vite,@builder.io/*}' --binaries --browsers` - render: shell - placeholder: System, Binaries, Browsers - validations: - required: true + required: false - type: textarea id: additional_information attributes: - label: Additional Information + label: Información Adicional validations: required: false From 29fd94a0e1b9d0767b95fc9cbf9bdba76d81744a Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 10:18:07 +0100 Subject: [PATCH 07/35] Update bug.yml --- .github/ISSUE_TEMPLATE/bug.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml index 098e9da..2d2f5a6 100644 --- a/.github/ISSUE_TEMPLATE/bug.yml +++ b/.github/ISSUE_TEMPLATE/bug.yml @@ -7,6 +7,17 @@ body: attributes: value: | Gracias por tomarte el tiempo de reportar este problema + + - type: dropdown + id: version + attributes: + label: ¿Que versión estas usando? + description: '__INFO:__ Recuerda que puedes consultar dudas directamente en [discord](https://link.codigoencasa.com/DISCORD)' + options: + - v2 + - v1 + validations: + required: true - type: dropdown id: component @@ -35,7 +46,7 @@ body: attributes: label: Reproducir error description: __(Recomendación)__ trata de grabar un video puedes usar algunas de las siguientes herramientas [https://www.vidyard.com/](https://www.vidyard.com/) [https://www.loom.com/](https://www.loom.com/) y en lo posbile apoyate en [https://stackblitz.com/](https://stackblitz.com/) para compartir el código de ser necesario - placeholder: Reproduction URL + placeholder: URL video o stackblitz validations: required: false From 4819dfebda20d2021b5769472320c92d120a18f7 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 10:23:24 +0100 Subject: [PATCH 08/35] Create config.yml --- .github/ISSUE_TEMPLATE/config.yml | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/config.yml diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..7590616 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,4 @@ +contact_links: + - name: 🤔 Core Team + url: https://link.codigoencasa.com/DISCORD + about: Si quieres formar parte del CoreTeam, patrocinar el proyecto o propuesta profesionales From 3e0781fde6e9eae2e81523dbff38f3ee7fe64c7e Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 10:26:27 +0100 Subject: [PATCH 09/35] Update PULL_REQUEST_TEMPLATE.md --- .github/PULL_REQUEST_TEMPLATE.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index b0feb3a..8278042 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,18 +1,12 @@ -# Cual version del BOT es? - -- [ ] v2 -- [ ] v1 - - -# Que tipo de ISSUE es? +# Que tipo de Pull Request es? - [ ] Mejoras - [ ] Bug - [ ] Docs / tests -# Description +# Descripción -Por favor agrega una descripción de tu problema para tener más contexto y poder ayudar más rápido. Si es de ayuda puedes usar plataformar como [https://www.loom.com/](https://www.loom.com/) para grabar un video. +Por favor agrega una descripción de tu aporte para tener más contexto y poder avanzar más rápido. Si es de ayuda puedes usar plataformar como [https://www.loom.com/](https://www.loom.com/) para grabar un video. > Forma parte de este proyecto. From b8ea8283ebcc1652dfd03f5aaf08bbf933f29626 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 10:39:17 +0100 Subject: [PATCH 10/35] Create auto-pr-issue.yml --- .github/auto-pr-issue.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 .github/auto-pr-issue.yml diff --git a/.github/auto-pr-issue.yml b/.github/auto-pr-issue.yml new file mode 100644 index 0000000..e36a213 --- /dev/null +++ b/.github/auto-pr-issue.yml @@ -0,0 +1,13 @@ +name: 'Close stale issues and PRs' +on: + schedule: + - cron: '30 1 * * *' + +jobs: + stale: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v6 + with: + stale-issue-message: 'Message to comment on stale issues. If none provided, will not mark issues stale' + stale-pr-message: 'Message to comment on stale PRs. If none provided, will not mark PRs stale' From fbaef0f60c89d3b4273ddf17ccf3b41acc2953c8 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 22:43:45 +0100 Subject: [PATCH 11/35] Update auto-pr-issue.yml --- .github/auto-pr-issue.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/auto-pr-issue.yml b/.github/auto-pr-issue.yml index e36a213..de858a9 100644 --- a/.github/auto-pr-issue.yml +++ b/.github/auto-pr-issue.yml @@ -1,7 +1,7 @@ name: 'Close stale issues and PRs' on: schedule: - - cron: '30 1 * * *' + - cron: '55 22 * * *' jobs: stale: From 407e9065e7022610e7209a04534ffc18589c7bdb Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:07:26 +0100 Subject: [PATCH 12/35] Update and rename auto-pr-issue.yml to stale-issues.yml --- .github/auto-pr-issue.yml | 13 ------------- .github/stale-issues.yml | 20 ++++++++++++++++++++ 2 files changed, 20 insertions(+), 13 deletions(-) delete mode 100644 .github/auto-pr-issue.yml create mode 100644 .github/stale-issues.yml diff --git a/.github/auto-pr-issue.yml b/.github/auto-pr-issue.yml deleted file mode 100644 index de858a9..0000000 --- a/.github/auto-pr-issue.yml +++ /dev/null @@ -1,13 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '55 22 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v6 - with: - stale-issue-message: 'Message to comment on stale issues. If none provided, will not mark issues stale' - stale-pr-message: 'Message to comment on stale PRs. If none provided, will not mark PRs stale' diff --git a/.github/stale-issues.yml b/.github/stale-issues.yml new file mode 100644 index 0000000..7efe801 --- /dev/null +++ b/.github/stale-issues.yml @@ -0,0 +1,20 @@ +name: Close inactive issues +on: + schedule: + - cron: "15 23 * * *" + +jobs: + close-issues: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v4 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + stale-issue-message: "This issue is stale because it has been open for 60 days with no activity." + close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale." + stale-issue-label: "stale" + exempt-issue-labels: "bug,enhancement" + days-before-issue-stale: 60 + days-before-issue-close: 14 + days-before-pr-stale: -1 + days-before-pr-close: -1 From 467cd234574f47f07f32cd45240e464e4fc5ca57 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:11:44 +0100 Subject: [PATCH 13/35] Update stale-issues.yml --- .github/stale-issues.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/stale-issues.yml b/.github/stale-issues.yml index 7efe801..afd0565 100644 --- a/.github/stale-issues.yml +++ b/.github/stale-issues.yml @@ -1,7 +1,7 @@ name: Close inactive issues on: schedule: - - cron: "15 23 * * *" + - cron: "*/5 * * * *" jobs: close-issues: From a80225f40eb8f6026334c98f584590355bd32c61 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:18:22 +0100 Subject: [PATCH 14/35] Create codeql.yml --- .github/workflows/codeql.yml | 76 ++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 .github/workflows/codeql.yml diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml new file mode 100644 index 0000000..9310bcc --- /dev/null +++ b/.github/workflows/codeql.yml @@ -0,0 +1,76 @@ +# For most projects, this workflow file will not need changing; you simply need +# to commit it to your repository. +# +# You may wish to alter this file to override the set of languages analyzed, +# or to provide custom queries or build logic. +# +# ******** NOTE ******** +# We have attempted to detect the languages in your repository. Please check +# the `language` matrix defined below to confirm you have the correct set of +# supported CodeQL languages. +# +name: "CodeQL" + +on: + push: + branches: [ "main", dev, next-release ] + pull_request: + # The branches below must be a subset of the branches above + branches: [ "main" ] + schedule: + - cron: '21 16 * * 5' + +jobs: + analyze: + name: Analyze + runs-on: ubuntu-latest + permissions: + actions: read + contents: read + security-events: write + + strategy: + fail-fast: false + matrix: + language: [ 'javascript' ] + # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ] + # Use only 'java' to analyze code written in Java, Kotlin or both + # Use only 'javascript' to analyze code written in JavaScript, TypeScript or both + # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support + + steps: + - name: Checkout repository + uses: actions/checkout@v3 + + # Initializes the CodeQL tools for scanning. + - name: Initialize CodeQL + uses: github/codeql-action/init@v2 + with: + languages: ${{ matrix.language }} + # If you wish to specify custom queries, you can do so here or in a config file. + # By default, queries listed here will override any specified in a config file. + # Prefix the list here with "+" to use these queries and those in the config file. + + # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs + # queries: security-extended,security-and-quality + + + # Autobuild attempts to build any compiled languages (C/C++, C#, Go, or Java). + # If this step fails, then you should remove it and run the build manually (see below) + - name: Autobuild + uses: github/codeql-action/autobuild@v2 + + # ℹ️ Command-line programs to run using the OS shell. + # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun + + # If the Autobuild fails above, remove it and uncomment the following three lines. + # modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance. + + # - run: | + # echo "Run, Build Application using script" + # ./location_of_script_within_repo/buildscript.sh + + - name: Perform CodeQL Analysis + uses: github/codeql-action/analyze@v2 + with: + category: "/language:${{matrix.language}}" From 7890eae03a70db0e4ea500c334c512c7e9f4f9a2 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:18:53 +0100 Subject: [PATCH 15/35] Delete stale-issues.yml --- .github/stale-issues.yml | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 .github/stale-issues.yml diff --git a/.github/stale-issues.yml b/.github/stale-issues.yml deleted file mode 100644 index afd0565..0000000 --- a/.github/stale-issues.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: Close inactive issues -on: - schedule: - - cron: "*/5 * * * *" - -jobs: - close-issues: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v4 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: "This issue is stale because it has been open for 60 days with no activity." - close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale." - stale-issue-label: "stale" - exempt-issue-labels: "bug,enhancement" - days-before-issue-stale: 60 - days-before-issue-close: 14 - days-before-pr-stale: -1 - days-before-pr-close: -1 From 1fa234c870e5d0a4306faa632076cc701ab9078f Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:19:11 +0100 Subject: [PATCH 16/35] Create stale-issues.yml --- .github/workflows/stale-issues.yml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .github/workflows/stale-issues.yml diff --git a/.github/workflows/stale-issues.yml b/.github/workflows/stale-issues.yml new file mode 100644 index 0000000..afd0565 --- /dev/null +++ b/.github/workflows/stale-issues.yml @@ -0,0 +1,20 @@ +name: Close inactive issues +on: + schedule: + - cron: "*/5 * * * *" + +jobs: + close-issues: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v4 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + stale-issue-message: "This issue is stale because it has been open for 60 days with no activity." + close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale." + stale-issue-label: "stale" + exempt-issue-labels: "bug,enhancement" + days-before-issue-stale: 60 + days-before-issue-close: 14 + days-before-pr-stale: -1 + days-before-pr-close: -1 From 55985083ec3e6d892e16d51129864c2dd420fe28 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:25:50 +0100 Subject: [PATCH 17/35] Create stale.yml --- .github/workflows/stale.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 .github/workflows/stale.yml diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml new file mode 100644 index 0000000..408bebd --- /dev/null +++ b/.github/workflows/stale.yml @@ -0,0 +1,27 @@ +# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time. +# +# You can adjust the behavior by modifying this file. +# For more information, see: +# https://github.com/actions/stale +name: Mark stale issues and pull requests + +on: + schedule: + - cron: '*/5 * * * *' + +jobs: + stale: + + runs-on: ubuntu-latest + permissions: + issues: write + pull-requests: write + + steps: + - uses: actions/stale@v5 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + stale-issue-message: 'Stale issue message' + stale-pr-message: 'Stale pull request message' + stale-issue-label: 'no-issue-activity' + stale-pr-label: 'no-pr-activity' From dabb0cf131bbb7f3cdfd709cbcf4dce0841c9e18 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:26:02 +0100 Subject: [PATCH 18/35] Delete stale-issues.yml --- .github/workflows/stale-issues.yml | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 .github/workflows/stale-issues.yml diff --git a/.github/workflows/stale-issues.yml b/.github/workflows/stale-issues.yml deleted file mode 100644 index afd0565..0000000 --- a/.github/workflows/stale-issues.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: Close inactive issues -on: - schedule: - - cron: "*/5 * * * *" - -jobs: - close-issues: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v4 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: "This issue is stale because it has been open for 60 days with no activity." - close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale." - stale-issue-label: "stale" - exempt-issue-labels: "bug,enhancement" - days-before-issue-stale: 60 - days-before-issue-close: 14 - days-before-pr-stale: -1 - days-before-pr-close: -1 From 77af8f9488e3bf839d501f6c60225d23af695264 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:32:04 +0100 Subject: [PATCH 19/35] Update stale.yml --- .github/workflows/stale.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 408bebd..313dbd9 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -7,7 +7,7 @@ name: Mark stale issues and pull requests on: schedule: - - cron: '*/5 * * * *' + - cron: '55 22 * * *' jobs: stale: From b7e1ae534a2661d36b7013864b0a63e51be21344 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 14 Dec 2022 23:33:34 +0100 Subject: [PATCH 20/35] Create SECURITY.md --- SECURITY.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..034e848 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,21 @@ +# Security Policy + +## Supported Versions + +Use this section to tell people about which versions of your project are +currently being supported with security updates. + +| Version | Supported | +| ------- | ------------------ | +| 5.1.x | :white_check_mark: | +| 5.0.x | :x: | +| 4.0.x | :white_check_mark: | +| < 4.0 | :x: | + +## Reporting a Vulnerability + +Use this section to tell people how to report a vulnerability. + +Tell them where to go, how often they can expect to get an update on a +reported vulnerability, what to expect if the vulnerability is accepted or +declined, etc. From 3842bb6889efff78bf5b47c445c74a70c9c35588 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 09:34:19 +0100 Subject: [PATCH 21/35] Update stale.yml --- .github/workflows/stale.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 313dbd9..0996017 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -3,7 +3,7 @@ # You can adjust the behavior by modifying this file. # For more information, see: # https://github.com/actions/stale -name: Mark stale issues and pull requests +name: Revisar ISSUES abandonadas on: schedule: @@ -21,7 +21,8 @@ jobs: - uses: actions/stale@v5 with: repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'Stale issue message' - stale-pr-message: 'Stale pull request message' + stale-issue-message: '¿Alguna novedad sobre esta ISSUE?' + stale-pr-message: '¿Alguna novedad sobre esta PULL REQUEST?' stale-issue-label: 'no-issue-activity' stale-pr-label: 'no-pr-activity' + exempt-issue-assignees: 'leifermendez' From 7e5533e46ed60fb2293095bb46a542aed79ee4dc Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:03:52 +0100 Subject: [PATCH 22/35] Create test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 61 ++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/test-case.yml diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml new file mode 100644 index 0000000..16429a9 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -0,0 +1,61 @@ +name: 🐬 Caso de uso +description: Reporta tu caso de uso y cuales fueron tus resultados +labels: [usecase] +title: '[🐬]' +body: + - type: markdown + attributes: + value: | + Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad + + - type: dropdown + id: version + attributes: + label: ¿Cual proveedor usaste? + description: 'Actualmente tenemos varios proveedores que sirven como punto de entrada y salida con Whatsapp' + options: + - whatsapp-web.js + - venom + - bailey + - twilio + - meta + validations: + required: true + + - type: dropdown + id: component + attributes: + label: ¿Cual base de datos usaste? + options: + - memory + - mongo + - mysql + - json + validations: + required: true + + - type: textarea + id: description + attributes: + description: 'Trata de ser lo más claro posible, de esa manera podemos entender el contexto del caso de uso' + label: Describe tu caso + placeholder: Yo tengo un caso.... + + validations: + required: true + + - type: checkboxes + id: terms + attributes: + label: Code of Conduct + description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com) + options: + - label: I agree to follow this project's Code of Conduct + required: true + + - type: textarea + id: additional_information + attributes: + label: Información Adicional + validations: + required: false From 8328f5a078660e95eb859d834f04287c37a5b3aa Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:04:51 +0100 Subject: [PATCH 23/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 16429a9..05e317f 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -50,6 +50,8 @@ body: label: Code of Conduct description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com) options: + - label: I agree to follow this project's Code of Conduct + - label: I agree to follow this project's Code of Conduct - label: I agree to follow this project's Code of Conduct required: true From a7d4103eb3f7b99153634939b5541848ab1d8849 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:05:04 +0100 Subject: [PATCH 24/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 05e317f..36053d5 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -50,9 +50,9 @@ body: label: Code of Conduct description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com) options: - - label: I agree to follow this project's Code of Conduct - - label: I agree to follow this project's Code of Conduct - - label: I agree to follow this project's Code of Conduct + - label: I agree to follow this prwoject's Code of Conduct + - label: I agree to follow this prqoject's Code of Conduct + - label: I agree to follow this prfoject's Code of Conduct required: true - type: textarea From 2b13d58077030c391770b369d27f1670ec276965 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:53:02 +0100 Subject: [PATCH 25/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 36053d5..98c6684 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -43,18 +43,13 @@ body: validations: required: true - - - type: checkboxes - id: terms + - type: textarea + id: logs attributes: - label: Code of Conduct - description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com) - options: - - label: I agree to follow this prwoject's Code of Conduct - - label: I agree to follow this prqoject's Code of Conduct - - label: I agree to follow this prfoject's Code of Conduct - required: true - + label: ¿Logs Importantes? + description: Si tienes algunos logs importantes a tener en cuenta o que muetren algun error en concreto. + render: shell + - type: textarea id: additional_information attributes: From 186477f04d73cc26fe32ad9845c20f3dd189c86c Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:56:29 +0100 Subject: [PATCH 26/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 98c6684..8571efb 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -40,9 +40,9 @@ body: description: 'Trata de ser lo más claro posible, de esa manera podemos entender el contexto del caso de uso' label: Describe tu caso placeholder: Yo tengo un caso.... - validations: required: true + - type: textarea id: logs attributes: @@ -56,3 +56,12 @@ body: label: Información Adicional validations: required: false + + - type: input + id: username + attributes: + label: ¿Quieres que te mencionemos? + description: Siempre buscamos fomentar la comunidad por lo cual si quieres que te mencionemos publicamente en nuestras redes sociales puedes dejar tu username + placeholder: @twitter o @github o @instagram o alguna url + validations: + required: false From 911965b48e088ef74bca21f29d2971a7a1592de7 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:57:19 +0100 Subject: [PATCH 27/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 8571efb..3398749 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -58,7 +58,7 @@ body: required: false - type: input - id: username + id: usernames attributes: label: ¿Quieres que te mencionemos? description: Siempre buscamos fomentar la comunidad por lo cual si quieres que te mencionemos publicamente en nuestras redes sociales puedes dejar tu username From 73e079e93abbb94c843ccb13915e205282bbaa81 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:57:41 +0100 Subject: [PATCH 28/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 3398749..d72839e 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -62,6 +62,6 @@ body: attributes: label: ¿Quieres que te mencionemos? description: Siempre buscamos fomentar la comunidad por lo cual si quieres que te mencionemos publicamente en nuestras redes sociales puedes dejar tu username - placeholder: @twitter o @github o @instagram o alguna url + placeholder: twitter o github o instagram o alguna url validations: required: false From 188ff4fb7dddccb656f4dfd7a9a1eb88df3511fd Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:58:59 +0100 Subject: [PATCH 29/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index d72839e..059971d 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -33,6 +33,17 @@ body: - json validations: required: true + + - type: dropdown + id: result + attributes: + label: Conclusion de la prueba + options: + - muy buena + - buena + - tiene errores + validations: + required: true - type: textarea id: description From e3cbf6af0179381186f1a7873455ddcc94d48de2 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 10:59:38 +0100 Subject: [PATCH 30/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 059971d..8b2491a 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -1,5 +1,5 @@ name: 🐬 Caso de uso -description: Reporta tu caso de uso y cuales fueron tus resultados +description: Reporta tu caso de uso y cuales fueron tus resultados \n puedes comenzar `npm create bot-whatsapp@dev` labels: [usecase] title: '[🐬]' body: From 032dc384b78575c1e816e35c74f1768097310ed1 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 11:00:08 +0100 Subject: [PATCH 31/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 8b2491a..cf5b43e 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -1,12 +1,12 @@ name: 🐬 Caso de uso -description: Reporta tu caso de uso y cuales fueron tus resultados \n puedes comenzar `npm create bot-whatsapp@dev` +description: Reporta tu caso de uso y cuales fueron tus resultados` labels: [usecase] title: '[🐬]' body: - type: markdown attributes: value: | - Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad + Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad \n puedes comenzar `npm create bot-whatsapp@dev - type: dropdown id: version From 83c247377a8834801c963210ce427897bff738c5 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 11:00:24 +0100 Subject: [PATCH 32/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index cf5b43e..704f480 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -1,12 +1,12 @@ name: 🐬 Caso de uso -description: Reporta tu caso de uso y cuales fueron tus resultados` +description: Reporta tu caso de uso y cuales fueron tus resultados labels: [usecase] title: '[🐬]' body: - type: markdown attributes: value: | - Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad \n puedes comenzar `npm create bot-whatsapp@dev + Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad \n puedes comenzar `npm create bot-whatsapp@dev` - type: dropdown id: version From 25fc864f66e9d3b099cdb844d61b3967791fd5b1 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 11:00:47 +0100 Subject: [PATCH 33/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 704f480..4aff898 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -6,7 +6,8 @@ body: - type: markdown attributes: value: | - Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad \n puedes comenzar `npm create bot-whatsapp@dev` + Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad + puedes comenzar `npm create bot-whatsapp@dev` - type: dropdown id: version From 5b15527d780e0edd13b890c9ffca9440dcf419d8 Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Thu, 15 Dec 2022 11:01:17 +0100 Subject: [PATCH 34/35] Update test-case.yml --- .github/ISSUE_TEMPLATE/test-case.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/test-case.yml b/.github/ISSUE_TEMPLATE/test-case.yml index 4aff898..e712610 100644 --- a/.github/ISSUE_TEMPLATE/test-case.yml +++ b/.github/ISSUE_TEMPLATE/test-case.yml @@ -6,8 +6,8 @@ body: - type: markdown attributes: value: | - Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad - puedes comenzar `npm create bot-whatsapp@dev` + Gracias por tomarte el tiempo de detallar este caso de uso, sera de gran utilidad para mantener un software de calidad puedes comenzar + ⚡ `npm create bot-whatsapp@dev` - type: dropdown id: version From e9539cab8b050045de81a2456b1fd9bb336cadee Mon Sep 17 00:00:00 2001 From: Leifer Mendez Date: Wed, 21 Dec 2022 09:54:15 +0100 Subject: [PATCH 35/35] added OpenCollective --- .github/FUNDING.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml index 1fde58c..95cd665 100644 --- a/.github/FUNDING.yml +++ b/.github/FUNDING.yml @@ -1,2 +1,3 @@ patreon: leifermendez custom: "https://www.buymeacoffee.com/leifermendez" +open_collective: bot-whatsapp