From d7e3d224d22b359befa1d661cdc0611d0e1ecb88 Mon Sep 17 00:00:00 2001 From: Hotel OS AI Manager Date: Sun, 1 Feb 2026 09:15:58 +0700 Subject: [PATCH] Migration to Cloud-First workflow --- .github/ISSUE_TEMPLATE/bug_report.yml | 95 +++++---------------------- .github/PULL_REQUEST_TEMPLATE.md | 24 +++++++ .github/workflows/ci.yml | 37 +++++++++++ .gitignore | 2 + 4 files changed, 81 insertions(+), 77 deletions(-) create mode 100644 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 .github/workflows/ci.yml create mode 100644 .gitignore diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index d228919e4e5..29612c46be7 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -1,102 +1,43 @@ name: Bug Report -description: File a bug report for Kiro -labels: ["pending-triage"] +description: Create a report to help us improve +labels: ["bug"] body: - type: markdown attributes: value: | - --- - ## ⚠️ Before you open this issue - - **Please ensure you're using the latest version of Kiro.** If you're an existing user or have been invited off the waitlist, use the [download links](https://kiro.dev/downloads/) to install or upgrade. Otherwise, join the [waitlist](https://kiro.dev/waitlist/) to get access. - - **Check if your issue is already known.** If so, **subscribe and comment to the following issues for updates** instead of opening a new one: - - [#195: Support for multi-root workspaces](https://github.com/kirodotdev/Kiro/issues/195) - [#194: Generate Commit Message" button for Kiro's Git integration](https://github.com/kirodotdev/Kiro/issues/194) - [#87: Remote SSH login issues](https://github.com/kirodotdev/Kiro/issues/87) - [#31: Provide a token counter in the chat window](https://github.com/kirodotdev/Kiro/issues/31) - - Thank you for helping us keep our issue tracker organized. - - --- - - type: markdown - attributes: - value: | - **Tip:** Use the `Report a bug / Suggest an idea` button in Kiro to automatically include your system info and conversation ID, then click `Preview on GitHub` to submit. - - type: checkboxes - attributes: - label: | - Before opening, please confirm: - options: - - label: I have [searched for duplicate or closed issues](https://github.com/kirodotdev/Kiro/issues?q=is%3Aissue+) - required: true - - type: input - id: os - attributes: - label: Operating System - description: Your operating system and version - placeholder: "e.g., macOS 14.2, Windows 11, Ubuntu 22.04" - validations: - required: true - - - type: input - id: kiro-version - attributes: - label: Kiro Version - description: The version of Kiro you're using - placeholder: "e.g., 1.2.3" - validations: - required: true - + Thanks for taking the time to fill out this bug report! - type: textarea id: bug-description attributes: label: Bug Description - description: Describe the issue you encountered - placeholder: "Describe the bug clearly and concisely. State which feature you used, your intended task, and how the bug affected your workflow." + description: A clear and concise description of what the bug is. validations: required: true - - type: textarea - id: reproduction-steps + id: steps-to-reproduce attributes: label: Steps to Reproduce - description: Provide steps to reproduce the issue - placeholder: | - 1. Open Kiro and create/open a project with [specific details] - 2. Perform action [be specific about what you did] - 3. Enter text/command [include exact text if relevant] - 4. Observe [describe the error or unexpected behavior in detail] - - Include any specific code, prompts, or files that are necessary to reproduce the issue. + description: | + 1. Go to '...' + 2. Click on '....' + 3. Scroll down to '....' + 4. See error validations: required: true - - type: textarea id: expected-behavior attributes: label: Expected Behavior - description: Describe what you expected to happen - placeholder: "Explain what Kiro should have done when you performed the actions above. Describe the intended outcome or behavior." + description: A clear and concise description of what you expected to happen. validations: required: true - - type: textarea - id: conversation-id + id: screenshots attributes: - label: Conversation ID - description: | - The conversation ID where the issue occurred (automatically populated when submitted from the IDE) - placeholder: "e.g., 1234-5678-9876" - validations: - required: false - - - type: textarea - id: additional-context + label: Screenshots + description: If applicable, add screenshots to help explain your problem. + - type: input + id: environment attributes: - label: Additional Context - description: Include supporting information that helps diagnose the issue - placeholder: "Add screenshots, error messages from logs, environment details (large codebase, custom configurations), or workarounds you attempted. This information helps diagnose and resolve the issue." - validations: - required: false + label: Environment + description: e.g. OS, Python version, etc. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 00000000000..205e9a67d65 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,24 @@ +## Description +Briefly describe the changes introduced by this PR. + +## Related Issue +Fixes # (issue) + +## Type of Change +- [ ] Bug fix (non-breaking change which fixes an issue) +- [ ] New feature (non-breaking change which adds functionality) +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) +- [ ] This change requires a documentation update + +## How Has This Been Tested? +Please describe the tests that you ran to verify your changes. + +## Checklist: +- [ ] My code follows the style guidelines of this project +- [ ] I have performed a self-review of my own code +- [ ] I have commented my code, particularly in hard-to-understand areas +- [ ] I have made corresponding changes to the documentation +- [ ] My changes generate no new warnings +- [ ] I have added tests that prove my fix is effective or that my feature works +- [ ] New and existing unit tests pass locally with my changes +- [ ] Any dependent changes have been merged and published in downstream modules diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml new file mode 100644 index 00000000000..2b2ba319ee4 --- /dev/null +++ b/.github/workflows/ci.yml @@ -0,0 +1,37 @@ +name: CI + +on: + push: + branches: [ main, master ] + pull_request: + branches: [ main, master ] + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v4 + + - name: Set up Python + uses: actions/setup-python@v5 + with: + python-version: '3.12' + + - name: Install dependencies + run: | + python -m pip install --upgrade pip + pip install flake8 pytest + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi + pip install -e . + + - name: Lint with flake8 + run: | + # stop the build if there are Python syntax errors or undefined names + flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics + # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide + flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics + + - name: Test with pytest + run: | + pytest diff --git a/.gitignore b/.gitignore new file mode 100644 index 00000000000..04747f66443 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +kimidev/ +.env