Skip to content
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

fix(editing-support): replace auto-save.nvim's url with its original repo #673

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

ryan4yin
Copy link
Contributor

@ryan4yin ryan4yin commented Dec 6, 2023

📑 Description

The fork repo http://github.com/zoriya/auto-save.nvim has been deleted by its owner, revert to the original repo.

Copy link

github-actions bot commented Dec 6, 2023

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

  • If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

  • If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

  • Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

  • README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

  • Proper usage of opts table rather than setting things up with the config function.

@ryan4yin ryan4yin changed the title fix(editing-support): auto-save.vim 404 not found fix(editing-support): replace auto-save.nvim's url with its original repo Dec 8, 2023
@Uzaaft Uzaaft merged commit 3c7cbc7 into AstroNvim:main Dec 8, 2023
15 checks passed
@ryan4yin ryan4yin deleted the dev-fix-autosave branch December 9, 2023 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants