-
Notifications
You must be signed in to change notification settings - Fork 16
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
add macos support #43
base: master
Are you sure you want to change the base?
Conversation
Kevin V seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Is there any update about this PR? |
@vietcgi while I appreciate you contributing to the PR, given the original author of the PR never agreed to the CLA, I can't merge this. Frankly, I don't use macOS and the CI tests don't support it, so macOS support would have been unofficial at best. Antigen itself hasn't had a release in 4 years, so should be considered unsupported at this point. I'm actually using a 5-year-old version of Antigen for this role because I had issues with later versions. I've been evaluating other Zsh plugin managers recently. I tried zplug, which is very easy to use, but slow on shell startup (https://github.com/gantsign/devcontainers/blob/main/devcontainer-base/config/zsh/zplugrc.zsh). I found zimfw much faster, but harder to use. I don't have a replacement Ansible role to suggest. If you want to use Antigen, I suggest you fork this role. Otherwise, consider using another Zsh plugin manager that's still being maintained. |
I've agreed to the CLA. It would be nice if you can merge this. |
Hi @vietcgi the CLA check is still failing because you used a different email address as the author of the first commit (Kevin at kevin-f.lan). This email address isn't associated with your Github account. You either need to associate that email address with your GitHub account (under the settings for your user), or change the author information of your first commit (assuming you are the author) and then force push to fix the CLA verification issue (https://stackoverflow.com/questions/3042437/how-to-change-the-commit-author-for-one-specific-commit). Feel free to flatten the commits if that makes it easier (I'll be flattening them anyway when I merge). |
No description provided.