Skip to content

assistant/supermaven-nvim: init #990

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

justDeeevin
Copy link

supermaven-nvim's README claims nvim-cmp integration is as simple as adding "supermaven" to the sources list, so I felt it unnecessary to add a separate option for that here. Let me know if that should be changed.

Also, this is my first time contributing here, so sorry if there's anything that doesn't fit standards. I referred to the other assistant options when writing this.

Copy link

github-actions bot commented Jul 5, 2025

🚀 Live preview deployed from c4d8027

View it here:

Debug Information

Triggered by: justDeeevin

HEAD at: add-supermaven

Reruns: 1049

@Soliprem Soliprem changed the title supermaven-nvim: add option assistant/supermaven-nvim: init Jul 5, 2025
Copy link
Collaborator

@Soliprem Soliprem left a comment

Choose a reason for hiding this comment

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

off the bat, that change will get it to build. On the rest, I'm unfamiliar with the workflow for Supermaven, but on the nix side (besides my reviews), things LGTM.

I recommend you use the checklist, regarding style and testing, that comes as the templates for new PRs :). It's great for first-time contributors to dodge "obvious" reviews and for long-time contributors as an actual checklist of things to remember (it's also just a bunch of things we don't have to wonder if you did, which makes reviewing easier).

Thanks for the work <3

p.s. It looks like it works correctly, but I noticed it downloading a binary? Unsure of where that's being stored

Copy link
Owner

@NotAShelf NotAShelf left a comment

Choose a reason for hiding this comment

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

Thank you for the good work. I'm leaving two comments for the sake of consistency with the project styles. Soliprem's comments also apply.

Lastly, please add a changelog entry before we can merge this.

@justDeeevin
Copy link
Author

justDeeevin commented Jul 5, 2025

I recommend you use the checklist

When I created the PR it didn't pre-fill the description with the template. Don't know why that happened! Thanks for your feedback in the face of this.

Also, apologies for not properly testing, I should have known better. I need to stop making midnight PRs🫠

@justDeeevin
Copy link
Author

I changed it to supermaven-nvim as requested. However, I still think supermaven would make more sense. The option for copilot is just assistant.copilot even though the plugin itself is called copilot-lua. Is there a particular rationale for this I'm not seeing?

@justDeeevin
Copy link
Author

p.s. It looks like it works correctly, but I noticed it downloading a binary? Unsure of where that's being stored

Reading the source code, it looks like this gets put in $XDG_DATA_HOME/supermaven (or $HOME/.supermaven if XDG_DATA_HOME is unset).

@justDeeevin justDeeevin requested a review from NotAShelf July 5, 2025 18:03
@NotAShelf
Copy link
Owner

I changed it to supermaven-nvim as requested. However, I still think supermaven would make more sense. The option for copilot is just assistant.copilot even though the plugin itself is called copilot-lua. Is there a particular rationale for this I'm not seeing?

Sorry for the late response. This is a relatively new "convention" that we've started applying in light of some future refactor plans. There are plugins that do not adhere to the convention yet, as they have been added before we even discussed such a naming decision. It'll be easier for everyone if you name the options after the plugins :)

@lackac
Copy link
Contributor

lackac commented Jul 5, 2025

When I created the PR it didn't pre-fill the description with the template. Don't know why that happened! Thanks for your feedback in the face of this.

I also noticed this. I'm always adding &template=pull_request_template.md to the end of the URL when creating a pull request. But if we want people to use the checklist, it should be automatic. I think the file could be moved to .github/pull_request_template.md if a single template is sufficient and that will make it apply automatically.

@NotAShelf
Copy link
Owner

I'm quite positive that the pull request template is active by default. Unless, of course, GH has changed how it functions. Last I've checked the template is "prompted" by default, and it's usable in CLI tools like gh. I'll look into it on monday.

@justDeeevin
Copy link
Author

What's left to do here?

NotAShelf
NotAShelf previously approved these changes Jul 7, 2025
@NotAShelf NotAShelf requested a review from Soliprem July 7, 2025 10:24
@NotAShelf
Copy link
Owner

can be merged with @Soliprem's approval.

Soliprem
Soliprem previously approved these changes Jul 7, 2025
Copy link
Collaborator

@Soliprem Soliprem left a comment

Choose a reason for hiding this comment

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

LGTM

@justDeeevin justDeeevin dismissed stale reviews from Soliprem and NotAShelf via 1cd70f7 July 8, 2025 15:29
github-actions bot pushed a commit that referenced this pull request Jul 8, 2025
@justDeeevin justDeeevin requested a review from NotAShelf July 8, 2025 15:34
@justDeeevin
Copy link
Author

justDeeevin commented Jul 8, 2025

CI was failing due to an oversight when renaming from supermaven to supermaven-nvim. fix pushed. Also force-pushed with rebase to resolve conflict.

@NotAShelf
Copy link
Owner

I'm sorry I've caused a merge conflict again, if you could resolve it I can merge this right away

@justDeeevin
Copy link
Author

So strange that that should cause a conflict.

Done!

github-actions bot pushed a commit that referenced this pull request Jul 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants