tedspare/maige

Issue-labeller powered by GPT.

maige's Issues

should open usage issue

test

Unlabelled issue

Old issue should be labelled

test usage alert

[Bug] test after app router migration

Very high priority bug: the UI is broken

This is high priority

Maige Usage

Thanks for trying Maige.

Running GPT-based services is pricey. At this point, we ask you to add payment info to continue using Maige.

Add payment info

Feel free to close this issue.

Add a column to track total usage

The customer schema would change to include a new field: totalUsage or something

needs approval: label should be added

[Test] the navbar is broken

it's broken

[Test] Maige Usage

Thanks for trying Maige.

Running GPT-based services is pricey. At this point, we ask you to add payment info to continue using Maige.

Add payment info

Feel free to close this issue.

[Test] UI is broken

This is very high priority

The UI is broken

This is very high priority

Maige is not working

Are labels being added?

The listener is returning a 404

In GitHub app settings, it shows a 404 for the latest requests with this message: "failed to process"

Post-install message is broken

The website throws a 404

The UI is broken

This is very high priority

this is a bug

the UI is broken

Issues are not being labelled

From Cal.com repo

Apply to old issues by mentioning @maige-bot

• From Peer: "can we retrofill these issues with priority labels from maige?"

Retrain via upvote/downvote comments

From Peer at Cal.com (our first external user):

• i mean: “How was my label decision, just upvote or downvote”
• To improve labelling over time

The UI is broken

This is very high priority

Refrain from labelling already-labelled issues

Requested by @ericallam for triggerdotdev/trigger.dev

If an issue is already labelled upon creation/trigger, avoid adding more labels

should now label issues successfully

Suggest similar issues when an issue is opened

The bot would add a comment listing 1-3 issues it thinks is relevant

Possible approach:

• On issue opened, fetch all (or some) open issues
• Map issues to title and first 300 chars of their body (could be cached in the future)
• Pass them to gpt-3.5-turbo, asking it to select 1-3 similar issues
• Put this all behind a maige check for duplicates command if too expensive
• Only run if >10 open issues

[Test] comments should not be added when labelling

Comments by Maige should only appear when prompted

very buggy bug

you guessed it

Give repo context to GPT

• Include a CODEOWNERS file if available
• Eventually, construct a codebase map to understand where a problem might arise

Old issue

Very stale outdated issue

Labels do not always show up

Add some monitoring or observability to figure out why labels don't apply, without an error message

missing openAI key

this should get labelled

[Test] this is a bug

It's a very big bad bug