Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the following:
Please help resolve this issue:
! This task does not reflect a business priority at the moment. You may start tasks with one of the following labels: Priority: 3 (High), Priority: 4 (Urgent), Priority: 5 (Emergency)
_Originally posted by @ubiquity-os[bot] in ubiquity/business-development#93
Repository: ShivTestOrg/command-start-stop
Issue #1
File tree:
/tmp/personal-agent-pbegp-Srb30Z
├── README.md
├── bun.lockb
├── dist
│ └── index.js
├── eslint.config.mjs
├── graphql.config.yml
├── jest.config.ts
├── manifest.json
├── package.json
├── src
│ ├── adapters
│ │ ├── index.ts
│ │ └── supabase
│ │ └── helpers
│ │ ├── supabase.ts
│ │ └── user.ts
│ ├── handlers
│ │ ├── result-types.ts
│ │ ├── shared
│ │ │ ├── check-assignments.ts
│ │ │ ├── check-task-stale.ts
│ │ │ ├── generate-assignment-comment.ts
│ │ │ ├── get-user-task-limit-and-role.ts
│ │ │ ├── start.ts
│ │ │ ├── stop.ts
│ │ │ ├── structured-metadata.ts
│ │ │ ├── table.ts
│ │ │ └── user-assigned-timespans.ts
│ │ └── user-start-stop.ts
│ ├── index.ts
│ ├── plugin.ts
│ ├── types
│ │ ├── command.ts
│ │ ├── context.ts
│ │ ├── env.ts
│ │ ├── index.ts
│ │ ├── payload.ts
│ │ └── plugin-input.ts
│ └── utils
│ ├── get-closing-issue-references.ts
│ ├── get-linked-prs.ts
│ ├── get-pull-requests-fallback.ts
│ ├── get-user-association.ts
│ ├── issue.ts
│ ├── list-organizations.ts
│ └── shared.ts
├── tests
│ ├── mocks
│ │ ├── db.ts
│ │ ├── handlers.ts
│ │ ├── issue-template.ts
│ │ ├── node.ts
│ │ ├── repo-template.json
│ │ ├── users-get.json
│ │ └── valid-configuration.json
│ ├── configuration.test.ts
│ ├── fallbacks.test.ts
│ ├── http
│ │ └── run.http
│ ├── main.test.ts
│ ├── roles.test.ts
│ └── start.test.ts
├── tsconfig.json
└── wrangler.toml
13 directories, 52 files
Changes made:
Let me try one final time to properly format the tool request to modify the start.ts file. First, let's read the current content:
Now, let's update the file with the new validation logic:
This implementation:
The error message will now look like:
! The following issues prevent this task from being started: ❌ No price label is set. A price label is required to calculate the task duration. ❌ This task does not reflect a business priority. Required labels: Priority: 3 (High), Priority: 4 (Urgent), Priority: 5 (Emergency)
This ensures users get complete information about what needs to be fixed, with the price label error shown first, followed by any other validation issues.
Token Usage: