Excluding Archived Repositories

[0x4007]

• Might be more accurate to exclude archived repositories. I see that its referencing Ask ChatGPT /ask ubiquity/ubiquibot#291.
• Also shouldn't the issue specification be at the top of its context?
• Lastly it might be good to exclude @UbiquityOS tagged comments from its context as well

Source: ubiquity/business-development#85

[Sadaf-A]

/start

[ubiquity-os-beta]

Warning!	This task was created over 58 days ago. Please confirm that this issue specification is accurate before starting.
Deadline	Fri, Dec 20, 11:37 PM UTC
Beneficiary	0x0BEd00438D57d07E3667b85Fa8EB86Af147C7025

Tip

• Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
• Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
• Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

[Sadaf-A]

@0x4007 Hey, could elaborate on the issue a little bit?

[0x4007]

This is the specific comment to reference ubiquity/business-development#85 (comment)

Follow the specification to improve the output of the ask command.

Archived repositories shouldn't be included as part of its context.

[Sadaf-A]

This is the specific comment to reference ubiquity/business-development#85 (comment)

Follow the specification to improve the output of the ask command.

Archived repositories shouldn't be included as part of its context.

I figured the rest of it out but I'm not sire how to go about this

Also shouldn't the issue specification be at the top of its context?

[0x4007]

Put the issue spec first in the context so that the LLM focuses on it more

[Sadaf-A]

https://github.com/ubiquity-os-marketplace/command-ask/blob/development/src%2Fhandlers%2Fask-llm.ts#L47-L50

@0x4007 here putting the issues on top of comments would do it? also I'm waiting for a review on my PR.

[ubiquity-os-beta]

Passed the disqualification threshold and no activity is detected, removing assignees: @Sadaf-A.