floe-dev/floe

AI writing assistants for docs and changelogs.

floe's Issues

GitHub-powered comments

[PRO-150] Review Action: Broken git diffs from outside org

When using the Review Action, the remote origin causes an issue if the head branch comes from anything other than the remote origin.

Example here: https://github.com/Floe-dev/floe/actions/runs/7530506512/job/20497371876?pr=62

_{From SyncLinear.com | PRO-150}

[PRO-155] Create empty commit on pr if the HEAD_SHA is from a user outside the org (forked branch)

Review comments do not currently work if the HEAD_SHA is from a forked branch. This is because the GH review comment API requires a commit_id, which in this case belong to a user outside the org. The method will thus give a 401.

A possible solution would be to create an empty commit if the HEAD_SHA is from outside the org. Then, pass the empty commit SHA to the review comment command.

Ideally, this functionality should be attached to a flag so that the org can determine if they want to opt into this functionality.

_{From SyncLinear.com | PRO-155}

[PRO-165] The Review Action is sometimes creating duplicate review comments

_{From SyncLinear.com | PRO-165}

[PRO-151] Add docs for Review Action

_{From SyncLinear.com | PRO-151}

Please register to enable the Korbit AI Mentor

Thank you for installing the Korbit AI Mentor!

To get started, please register an account on our website by authenticating with GitHub authentication. If you already have an account with us, please make sure it is linked to your GitHub account.

Once registered, we'll start reviewing your pull requests and you can kick of a scan manually from our website.

Please register to enable the Korbit AI Mentor

Thank you for installing the Korbit AI Mentor!

To get started, please register an account on our website by authenticating with
GitHub authentication. If you already have an account with us, please make sure it is linked to your GitHub account.

Once registered, we'll start reviewing your pull requests and you can kick of a scan manually from our website.

[PRO-156] Add seed data to db for local env

This will devs get setup quickly. Should contain seed data for a user, session, and workspace

_{From SyncLinear.com | PRO-156}

[PRO-162] Hide review results where the suggestions is the same as the original line

The language model will occasionally give an answer like this, especially on less powerful models. We can omit these results.

Example:

_{From SyncLinear.com | PRO-162}

[PRO-133] Ability to delete API keys

The dashboard currently doesn't have a way to delete keys.

_{From SyncLinear.com | PRO-133}

[PRO-152] Clicking the Signin button multiple creates multiple requests

The Signin button should enter a loading state and be disabled after the first click.

_{From SyncLinear.com | PRO-152}

[PRO-157] Improvements to Review results

The AI for the Reviews feature will sometimes return subpar results. For example:

• The AI might not catch some clear rule violations (eg. it does not find a spelling mistake)
• It returns a weird result. For example, it may say a sentence is missing a comma, when it isn't
• The results might not be consistent for the same block of text. This is despite having temperature set to 0, and the seed param set in the GPT request

In general, results seem to be worse when running against a lot of content in one request (eg. when running against an entire file).

Some ideas for how this can be improved:

• Chunk requests into even small chunks. Perhaps dividing by paragraph or line count.
  • Subdividing will use more tokens on the first request, but should result in fewer tokens across multiple requests due to caching
• Asking for a max limit on results
• Fine-tuning
• Prompt updates. For example, would a 'chain of thought'-style prompt yield better results?

_{From SyncLinear.com | PRO-157}