Skip to content
Closed

Dev #57

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
10de143
feat: #86eu4pn7j - add CheckboxInput component with customizable opti…
SomiVista Jul 11, 2025
4063b9f
feat: #86eu4pn7j - enhance CheckboxInput component with single checkb…
SomiVista Jul 11, 2025
fc9347d
feat: #86eu4pn7j - add new icons for lock open, eye, and eye off; upd…
SomiVista Jul 11, 2025
ed45091
feat: #86eu4pn7j - add new icons for lock open, eye, and eye off; upd…
SomiVista Jul 14, 2025
965077b
feat: #86eu4pn7j - enhance CheckboxInput stories with detailed docume…
SomiVista Jul 14, 2025
4d4ebd9
Merge branch 'CU-86eu4pn7j_Add-Checkbox-and-Radio-Input-component_som…
SomiVista Jul 14, 2025
67c633a
Merge pull request #54 from codebridger/CU-86eu4pn7j_Add-Checkbox-and…
navidshad Jul 19, 2025
4efe6a6
chore(release): 1.17.0-dev.23 [skip ci]
semantic-release-bot Jul 19, 2025
c4d33ff
fix: resolve issues with CheckboxInput component functionality and do…
navidshad Jul 19, 2025
e18af14
chore(release): 1.17.0-dev.24 [skip ci]
semantic-release-bot Jul 19, 2025
96a5a0f
chore: update release configuration for changelog file handling
navidshad Jul 19, 2025
1219771
Merge remote-tracking branch 'origin/main' into dev
navidshad Jul 19, 2025
b518ce0
chore: update PR description generator to use gpt-4.1-mini-2025-04-14…
navidshad Jul 19, 2025
71acacc
chore: add PR template and AI PR bot workflow, remove old description…
navidshad Jul 19, 2025
774920e
chore: comment out require_trigger in AI PR bot workflow configuration
navidshad Jul 19, 2025
f03c355
chore: rename AI PR bot workflow to CodePress Review and update model…
navidshad Jul 19, 2025
452f629
chore: add a PR description template and update AI PR bot workflow co…
navidshad Jul 19, 2025
e4c7343
chore: enhance AI PR bot workflow with additional configuration optio…
navidshad Jul 19, 2025
4473202
chore: update AI PR bot workflow to refine pull request trigger types…
navidshad Jul 19, 2025
d492f3d
chore: remove AI PR bot workflow file as part of project restructuring
navidshad Jul 19, 2025
226fe83
chore: update CodePress Review workflow to remove pull request trigge…
navidshad Jul 19, 2025
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
89 changes: 89 additions & 0 deletions .cursor/rules/pr_template.mdc
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
# Pull Request Description

> **Note**: Not all sections are required for every PR. Use only the sections that are relevant to your changes. Focus on the most important information for your specific pull request.

## 📋 Overview & Changes
<!-- Provide a brief summary of what this PR accomplishes and key changes -->

### 🎯 What was implemented
- [ ] Feature A
- [ ] Feature B
- [ ] Bug fix for issue C

### 📝 Commit Summary
<!--
Summary generated from commit messages and code changes:
- Key features implemented
- Bug fixes applied
- Files modified
- Breaking changes
- Performance improvements
- Code refactoring
-->

### 🔧 Technical Details
<!-- Provide technical implementation details if relevant -->

## 🔗 Related Tasks & Commit Analysis
<!-- Task tracking and commit analysis section -->

### 🔍 Task IDs & Links from Commits
<!--
Task IDs extracted from commit messages and their ClickUp links:
- Format: #task-id or CU-task-id
- ClickUp Link: https://app.clickup.com/t/[task-id]
- Example: #12345 → https://app.clickup.com/t/12345

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏 PRAISE: This is an excellent and comprehensive PR template that will greatly help contributors provide clear and structured PR descriptions, making reviews smoother and higher quality.

-->

## 🧪 Testing
<!-- Describe how the changes were tested -->

- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing completed
- [ ] Cross-browser testing (if applicable)

## 🔍 Review Checklist

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏 PRAISE: Great addition of a detailed and structured PR template! This will
help contributors provide comprehensive descriptions, improving
review quality and consistency.


Resolved by CodePress Review

The detailed PR template added here follows a clear structure and will improve review quality and consistency, addressing the praise comment on PR template quality.

<!-- Use this checklist to ensure your PR is ready for review -->

### Code Quality
- [ ] Code follows project coding standards
- [ ] No console.log statements left in production code
- [ ] No hardcoded values that should be configurable
- [ ] Proper error handling implemented
- [ ] Code is properly documented

### Performance
- [ ] No performance regressions introduced

### Security
- [ ] No security vulnerabilities introduced
- [ ] Input validation implemented where necessary
- [ ] Sensitive data properly handled

### Accessibility
- [ ] WCAG guidelines followed
- [ ] Keyboard navigation works properly
- [ ] Screen reader compatibility tested

## 🚀 Deployment Notes
<!-- Any special considerations for deployment -->

## 📚 Documentation
<!-- Update any relevant documentation -->

- [ ] README updated (if applicable)
- [ ] API documentation updated (if applicable)
- [ ] Component documentation updated (if applicable)

## 🔄 Breaking Changes

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: Consider adding example entries in the Breaking Changes section to
guide contributors on how to document breaking API or behavior changes.


Resolved by CodePress Review

The Breaking Changes section is present in the template. However, it does not yet include example entries. This comment remains relevant.

<!-- List any breaking changes that might affect other parts of the system -->

## 📋 Additional Notes
<!-- Any other information that reviewers should know -->

---

**Template Version**: 1
**Last Updated**: 19 Jun 2025
**Summary Source**: Commit messages and code changes
39 changes: 39 additions & 0 deletions .github/workflows/auto-pr-code-review.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# https://github.com/marketplace/actions/codepress-review
# How to use:
# 1. Add the following to your PR description:
# @codepress/review

name: CodePress Review

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏 PRAISE: Great job adding the CodePress Review GitHub Actions workflow. This automated AI review integration will help maintain high code quality and consistency on pull requests.


on:
pull_request:
types: []
issue_comment:
types: [created]
workflow_dispatch: # Allows manual triggering from the Actions tab

permissions:
pull-requests: write
contents: read
issues: read # Required to read PR comments

jobs:
ai-review:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
ref: ${{ github.event.issue.pull_request && format('refs/pull/{0}/head', github.event.issue.number) || github.ref }}

- name: CodePress Review

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: Consider enabling the comment trigger phrase for more flexible manual AI reviews on demand (currently disabled by run_on_comment_trigger: false). This could be helpful during ongoing PR discussions.

uses: quantfive/codepress-review@v2
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
model_provider: "openai"
model_name: "gpt-4.1-mini-2025-04-14"
openai_api_key: ${{ secrets.OPENAI_API_KEY_FOR_PR_DESC_GENERATOR }}
# Comment triggers are enabled by default
run_on_comment_trigger: false # Disable comment triggers
# comment_trigger_phrase: "@codepress/review" # Default
21 changes: 21 additions & 0 deletions .github/workflows/auto-pr-description.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
name: Pull Request Text Generator Workflow

on:
pull_request_target:
types: [opened, reopened, synchronize]

jobs:
generate-pr-text:
runs-on: ubuntu-latest
steps:
- name: Generate PR Description
uses: vblagoje/pr-auto@v1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: This workflow uses the secret OPENAI_API_KEY_FOR_PR_DESC_GENERATOR. Please ensure this secret is properly configured in the repository settings to prevent workflow failures.

id: pr_auto
with:
openai_api_key: ${{ secrets.OPENAI_API_KEY_FOR_PR_DESC_GENERATOR }}

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: Verify that the secret OPENAI_API_KEY_FOR_PR_DESC_GENERATOR is correctly configured in the repository settings to avoid workflow failures due to missing credentials.


Resolved by CodePress Review

The workflow includes the usage of the secret OPENAI_API_KEY_FOR_PR_DESC_GENERATOR, matching the existing comment; however, no changes to secret management are shown, so it remains relevant and unresolved.

system_prompt: ./custom-codepress-summary-prompt.md

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: Confirm that the referenced system prompt file 'custom-codepress-summary-prompt.md' is correctly configured and placed in the repository for the OpenAI model to generate meaningful PR descriptions.


Resolved by CodePress Review

The workflow adds usage of the system prompt file 'custom-codepress-summary-prompt.md' as in the existing comment; the comment remains relevant and not yet addressed by this diff.


- name: Update PR description
uses: vblagoje/update-pr@v1
with:
pr-body: ${{ steps.pr_auto.outputs.pr-text }}
17 changes: 11 additions & 6 deletions .releaserc.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,20 @@
{
"preset": "angular",
"releaseRules": [
{"type": "refactor", "release": "patch"}
{

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: The indentation in the "refactor" releaseRules has changed but does not add functional value. Consider cleaning formatting for consistency.


Resolved by CodePress Review

The indentation inconsistency noted previously for the "refactor" releaseRules entry has been cleaned up and is now consistent.

"type": "refactor",
"release": "patch"
}
]
}
],
"@semantic-release/release-notes-generator",
{
"path": "@semantic-release/changelog",
"condition": "branch.name === 'main'"
},
[

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: Introducing branch-specific changelog files (CHANGELOG.md for main, CHANGELOG-DEV.md for others) is a helpful improvement for multi-branch release workflows.


Resolved by CodePress Review

The configuration now introduces branch-specific changelog files using a ternary expression, which aligns with the previous suggestion and implements the intended behavior.

"@semantic-release/changelog",
{
"changelogFile": "${branch.name === 'main' ? 'CHANGELOG.md' : 'CHANGELOG-DEV.md'}"
}
],
[
"@semantic-release/npm",
{
Expand All @@ -34,7 +39,7 @@
{
"assets": [
"package.json",
"CHANGELOG.md"
"${branch.name === 'main' ? 'CHANGELOG.md' : 'CHANGELOG-DEV.md'}"
],
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
}
Expand Down
91 changes: 91 additions & 0 deletions custom-codepress-summary-prompt.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,91 @@
Take all below stracture to write a proper PR description

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 OPTIONAL: Minor typo in the first line: "stracture" should be "structure".

Suggested change
Take all below stracture to write a proper PR description
Take all below structure to write a proper PR description

Resolved by CodePress Review

The existing comment pointed out the typo "stracture", which remains uncorrected in this diff. Therefore, it is not resolved.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 NIT: There is a minor typo in the first line: "stracture" should be "structure".

Suggested change
Take all below stracture to write a proper PR description
Take all below structure to write a proper PR description


# Pull Request Description

> **Note**: Not all sections are required for every PR. Use only the sections that are relevant to your changes. Focus on the most important information for your specific pull request.

## 📋 Overview & Changes
<!-- Provide a brief summary of what this PR accomplishes and key changes -->

### 🎯 What was implemented
- [ ] Feature A
- [ ] Feature B
- [ ] Bug fix for issue C

### 📝 Commit Summary
<!--
Summary generated from commit messages and code changes:
- Key features implemented
- Bug fixes applied
- Files modified
- Breaking changes
- Performance improvements
- Code refactoring
-->

### 🔧 Technical Details
<!-- Provide technical implementation details if relevant -->

## 🔗 Related Tasks & Commit Analysis
<!-- Task tracking and commit analysis section -->

### 🔍 Task IDs & Links from Commits
<!--
Task IDs extracted from commit messages and their ClickUp links:
- Format: #task-id or CU-task-id
- ClickUp Link: https://app.clickup.com/t/[task-id]
- Example: #12345 → https://app.clickup.com/t/12345
-->

## 🧪 Testing
<!-- Describe how the changes were tested -->

- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing completed
- [ ] Cross-browser testing (if applicable)

## 🔍 Review Checklist
<!-- Use this checklist to ensure your PR is ready for review -->

### Code Quality
- [ ] Code follows project coding standards
- [ ] No console.log statements left in production code
- [ ] No hardcoded values that should be configurable
- [ ] Proper error handling implemented
- [ ] Code is properly documented

### Performance
- [ ] No performance regressions introduced

### Security
- [ ] No security vulnerabilities introduced
- [ ] Input validation implemented where necessary
- [ ] Sensitive data properly handled

### Accessibility
- [ ] WCAG guidelines followed
- [ ] Keyboard navigation works properly
- [ ] Screen reader compatibility tested

## 🚀 Deployment Notes
<!-- Any special considerations for deployment -->

## 📚 Documentation
<!-- Update any relevant documentation -->

- [ ] README updated (if applicable)
- [ ] API documentation updated (if applicable)
- [ ] Component documentation updated (if applicable)

## 🔄 Breaking Changes
<!-- List any breaking changes that might affect other parts of the system -->

## 📋 Additional Notes
<!-- Any other information that reviewers should know -->

---

**Template Version**: 1
**Last Updated**: 19 Jun 2025
**Summary Source**: Commit messages and code changes
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -85,4 +85,4 @@
"vite": "4.5.1",
"vue-tsc": "^0.40.4"
}
}
}

@github-actions github-actions Bot Jul 19, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ FYI: This diff is a trivial formatting edit (newline removal at end of file). No functional change. Consider adding a newline at end of file for POSIX compliance and to avoid potential warnings from some tools.


Resolved by CodePress Review

The diff reintroduces the lack of a newline at the end of the file, so the previous guidance remains unaddressed.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 NIT: Consider adding a newline at the end of this file to follow POSIX standards and avoid warnings from some tools.

Loading