mirror of
https://github.com/domfelipe/vibeflow-n8n.git
synced 2026-08-07 10:16:40 +00:00
feat: launch Vibeflow n8n v0.5.0
This commit is contained in:
commit
097f35215f
60 changed files with 2831 additions and 0 deletions
20
.github/DISCUSSION_TEMPLATE/ideas.yml
vendored
Normal file
20
.github/DISCUSSION_TEMPLATE/ideas.yml
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
title: Ideas
|
||||
labels: [ideas]
|
||||
body:
|
||||
- type: textarea
|
||||
id: summary
|
||||
attributes:
|
||||
label: Idea summary
|
||||
description: What would you like to see in Vibeflow n8n?
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: problem
|
||||
attributes:
|
||||
label: Problem
|
||||
description: What problem would this solve?
|
||||
- type: textarea
|
||||
id: sketch
|
||||
attributes:
|
||||
label: Proposed approach
|
||||
description: Share a rough implementation idea or usage example.
|
||||
15
.github/DISCUSSION_TEMPLATE/show-and-tell.yml
vendored
Normal file
15
.github/DISCUSSION_TEMPLATE/show-and-tell.yml
vendored
Normal file
|
|
@ -0,0 +1,15 @@
|
|||
title: Show and tell
|
||||
labels: [show-and-tell]
|
||||
body:
|
||||
- type: textarea
|
||||
id: built
|
||||
attributes:
|
||||
label: What did you build?
|
||||
description: Share the workflow, recipe, or automation you created with Vibeflow n8n.
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: notes
|
||||
attributes:
|
||||
label: Notes
|
||||
description: What worked well, what was tricky, and what should improve?
|
||||
28
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
28
.github/ISSUE_TEMPLATE/bug_report.md
vendored
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
name: Bug report
|
||||
about: Report a problem in behavior, docs, examples, or packaging
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Describe the bug.
|
||||
|
||||
## Expected behavior
|
||||
|
||||
What should have happened?
|
||||
|
||||
## Actual behavior
|
||||
|
||||
What happened instead?
|
||||
|
||||
## Where it appears
|
||||
|
||||
- [ ] docs
|
||||
- [ ] prompt / skill behavior
|
||||
- [ ] examples
|
||||
- [ ] client guide
|
||||
- [ ] recipes
|
||||
|
||||
## Additional context
|
||||
|
||||
Add logs, screenshots, or reproduction notes.
|
||||
5
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
5
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
blank_issues_enabled: true
|
||||
contact_links:
|
||||
- name: Questions and setup help
|
||||
url: https://github.com/OWNER/REPO/discussions
|
||||
about: Use Discussions for setup questions, ideas, and help requests.
|
||||
20
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
20
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
name: Feature request
|
||||
about: Suggest an improvement, new recipe, or new client support idea
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
Describe the improvement.
|
||||
|
||||
## Why it matters
|
||||
|
||||
What problem does it solve?
|
||||
|
||||
## Proposed shape
|
||||
|
||||
Describe your preferred implementation.
|
||||
|
||||
## Additional context
|
||||
|
||||
Links, examples, or related tools.
|
||||
25
.github/ISSUE_TEMPLATE/good-first-issue.md
vendored
Normal file
25
.github/ISSUE_TEMPLATE/good-first-issue.md
vendored
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
name: Good first issue
|
||||
about: Template for starter tasks to help new contributors join the project.
|
||||
title: "[good first issue] "
|
||||
labels: ["good first issue"]
|
||||
assignees: []
|
||||
---
|
||||
|
||||
## Goal
|
||||
|
||||
Describe the task in one or two sentences.
|
||||
|
||||
## Why it matters
|
||||
|
||||
Explain how this improves the project.
|
||||
|
||||
## Acceptance criteria
|
||||
|
||||
- [ ]
|
||||
- [ ]
|
||||
- [ ]
|
||||
|
||||
## Helpful context
|
||||
|
||||
Add links, files, or examples that make this easier to complete.
|
||||
17
.github/labels-suggested.md
vendored
Normal file
17
.github/labels-suggested.md
vendored
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
# Suggested labels
|
||||
|
||||
Create these labels after launch:
|
||||
|
||||
- good first issue
|
||||
- help wanted
|
||||
- documentation
|
||||
- recipes
|
||||
- schemas
|
||||
- design
|
||||
- release
|
||||
- ideas
|
||||
- show-and-tell
|
||||
- client:codex
|
||||
- client:claude-code
|
||||
- client:opencode
|
||||
- client:openclaude
|
||||
14
.github/pull_request_template.md
vendored
Normal file
14
.github/pull_request_template.md
vendored
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
## What changed
|
||||
|
||||
Describe the main changes in this PR.
|
||||
|
||||
## Why
|
||||
|
||||
Explain the problem or improvement.
|
||||
|
||||
## Checklist
|
||||
|
||||
- [ ] Docs updated if behavior changed
|
||||
- [ ] Examples updated if needed
|
||||
- [ ] Changelog updated if user-visible
|
||||
- [ ] No unsafe assumptions introduced
|
||||
10
.github/release-checklist.md
vendored
Normal file
10
.github/release-checklist.md
vendored
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
# Release checklist
|
||||
|
||||
- bump `VERSION`
|
||||
- update `CHANGELOG.md`
|
||||
- verify README links
|
||||
- verify placeholder endpoints are clearly marked
|
||||
- test one workflow recipe end to end
|
||||
- create Git tag
|
||||
- publish GitHub release notes
|
||||
- announce supported clients and best-effort clients clearly
|
||||
16
.github/workflows/markdown-lint.yml
vendored
Normal file
16
.github/workflows/markdown-lint.yml
vendored
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
name: Markdown Check
|
||||
|
||||
on:
|
||||
push:
|
||||
pull_request:
|
||||
|
||||
jobs:
|
||||
markdown-check:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: List markdown files
|
||||
run: |
|
||||
find . -type f \( -name "*.md" -o -name "VERSION" \) | sort
|
||||
Loading…
Add table
Add a link
Reference in a new issue