-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[+layer/php] Fix missed packages #14581
[+layer/php] Fix missed packages #14581
Conversation
Alternatively you can install these packages from their git repository. That's more conservative than removing them. |
Do we have maintained alternatives for these packages? If we have we should simply remove them and switch to the newer ones. Keeping the archived repo may be a work around but as it is not maintained anymore the chance that it will break randomly is pretty high. Maybe part of the functionality can be obtained by the integrated PHP lsp servers. |
I'm not aware if there are alternatives, but I have no idea where to look for them. I personally do not use those packages, so I don't have strong opinion regarding update or remove them. The approach proposed by @lebensterben looks safer, I'm going to apply the suggestion for now. And next I'll try to figure out if their functionality is provided by lsp (formatting definitely works, not sure about snippets). |
/rebase 🤔 @duianto yeah that rebase via comment thingy works now. For some reason it doesn't run most of the tests so it's probably useless for us. |
@lebensterben @smile13241324 How can we come to a conclusion? Should we keep the packages or remove them? @bystrano Proposed to remove phpcbf in #14574. Should I remove phpcbf and leave the other package? |
Let's go with the safer choice for now.
Interesting, I didn't know about rebasing via a comment.
It might still be useful to be able to rebase and re-run the tests manually. |
It seems to also rebase when the |
Done fetching from github. |
Could you squash the commits into one. |
Ready. I thought it can be done when merging a PR. Mixed up with GitLab, probably. |
Yeah, there might be a difference between them if the squash and merge is not fast-forward, it'll create a merge-commit. The rebase and merge doesn't create a merge commit, if I understand correctly. |
Thank you for contributing to Spacemacs. |
Thank you for taking care of this PR :-) |
Thank you for suggesting a fix. |
I removed /rebase since it doesn't trigger tests. And there is no clean workaround. Also it's a bit confusing for PR authors. Looks like it can work with private token cirrus-actions/rebase#65 🤔 |
How do you guys fix this package by download using git ? where should i put the file ? can anyone elaborate more about the step ? |
@differentMonster just update your spacemacs distribution: # For Linux
git -C ~/.emacs.d pull |
@Zebradil so after i git clone the package to the +lang folder and do the git -C ~/.emacs.d pull ? i have this error |
you'd can git add + git commit your local change or git restore to discard your local changes or git stash to save your local changes in stash If you've no idea what's going on, delete .emacs.d and reinstall. |
@differentMonster you do not need to clone any package additionally. Just update the spacemacs, it already includes changes from this PR. |
@lebensterben @Zebradil Got it work guys, thanks you guys guidelines and update the spacemacs package 👯 |
Fetch packages, which can't be found in Melpa anymore, from their GitHub repos:
Fixes #14381