Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
76 changes: 38 additions & 38 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,38 +1,38 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''
---
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
20 changes: 10 additions & 10 deletions .github/ISSUE_TEMPLATE/custom.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
name: Custom issue template
about: Describe this issue template's purpose here.
title: ''
labels: ''
assignees: ''

---


---
name: Custom issue template
about: Describe this issue template's purpose here.
title: ''
labels: ''
assignees: ''
---
40 changes: 20 additions & 20 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ''
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ''
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
49 changes: 26 additions & 23 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,23 +1,26 @@
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# dependencies
/node_modules
/.pnp
.pnp.js

# testing
/coverage

# production
/build

# misc
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local

npm-debug.log*
yarn-debug.log*
yarn-error.log*
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.

# dependencies
/node_modules
/.pnp
.pnp.js

# testing
/coverage

# production
/build

# misc
.DS_Store
.env.local
.env.development.local
.env.test.local
.env.production.local

npm-debug.log*
yarn-debug.log*
yarn-error.log*

#AI
.opencode
20 changes: 20 additions & 0 deletions .opencode/commands/commit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
description: Make commit
agent: build
---

# Commits - Como deben ser

Segun los cambios hechos, haz commit de ellos. El formato del primer mensaje es en ingles, inicia con un titulo corto sin un tag del tipo fea, fix, docs, etc y empezando en mayusculas (ej: "Fix + lo que se arreglo", "Add + lo que se agrego") y un segundo mensaje usando el -m una descripcion breve de menos de 50 caracteres iniciando con una sangria(ej: "- el procedimiento que se hizo y porque"). Despues de hacer commit, haz push, pero antes de hacer push 1) dile al usuario que ya hiciste commit de los cambios, 2) preguntale si puedes hacer push a la rama (sea ```git push``` o ```git push --set-upstream origin nombre-de-rama``` si es una nueva) y 3) dale dos opciones para seleccionar antes de continuar: **Si** para confirmar que si puedes hacer push y **No** para confirmar que no puedes hacer push a la rama. Si responde que **Si** haz push, si responde que **No**, termina de responder.

## Ramas - Como deben ser

Los nombres de las ramas deben ser asi:

``tipo-de-rama/nombre```

Ejemplos

- feature: ```feature/nombre-de-feature```.
- bugfix: ```bugfix/nombre-bugfix```.
- docs: ```docs/nombre-docs```.
9 changes: 9 additions & 0 deletions .opencode/commands/test.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
description: Run tests
agent: build
---

# Tests - instrucciones

Segun los cambios hechos, crea los tests necesarios o edita los que ya existen. Ejecuta todos los tests y muestra las fallas.
Enfocate en los tests fallidos y sugiere correcciones y soluciones.
Loading