Closed Freed-Wu closed 1 year ago
I understand the reason, but I can't think of a situation where ._zinit
would be added to git?
a situation where ._zinit would be added to git
Exist, such as user use ~/.local/share/zinit/plugins/XXX
to develop their own
plugin and use git to VCS.
Can you rebase your branch onto main so the checks will pass?
OK.
Seems that some test failed.
What happened? @vladdoster
Downloading alist-org/alist…
gh-r: failed to find the correct GitHub release asset to download.
What happened? @vladdoster
Downloading alist-org/alist… gh-r: failed to find the correct GitHub release asset to download.
Is it due to network problem? Can anyone rerun the test to take a look?
@vladdoster @pschmitt
@vladdoster @pschmitt
Don't. Fix the ci instead.
@Freed-Wu,
Your branch is out of date. Rebase your branch using the zdharma-continuum main branch.
@Freed-Wu,
I went ahead and rebased your branch.
@Freed-Wu,
Don't worry about the numerous commits. I'll merge this once unit tests pass and will regenerate the docs in a separate PR.
Thanks again for your PR :^)
All checks have passed.
Description
Create
._zinit/.gitignore
which content is '*' for every plugin.Motivation and Context
zinit create
._zinit
to store some metadata. However, this metadata should not be added to git.Related Issue(s)
Fix #395.
I am not sure if https://github.com/zdharma-continuum/zinit/blob/main/share/template-plugin/zsh.gitignore#L12 should be removed. Maybe we should support old zinit? And I think this file should be pushed to https://github.com/github/gitignore/ to let more zsh plugin developers use.
How Has This Been Tested?
I have tested it can work for me.
Types of changes
Checklist: