We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Instead of keeping two differents repositories of site configs, it could be better to contribute to the official site config repo from @fivefilters: https://github.com/fivefilters/ftr-site-config
So we need to extract site configs from wallabag v1 (here: https://github.com/wallabag/wallabag/tree/master/inc/3rdparty/site_config/standard) and merge them in the fivefilters repo.
The text was updated successfully, but these errors were encountered:
I think this depends if @fivefilters agrees (and is able to !) to update it fast enough when we PR it.
Sorry, something went wrong.
As far as I can see, he is fast enough.
Yeah, it seems so. Right.
Backport site_config changes from wallabag v1
cbba2d9
Fix wallabag/wallabag#1414
Is this issue needed for next alpha?
It's not a must have, it's a nice to have.
Le 6 janv. 2016 à 09:09, Nicolas Lœuillet notifications@github.com a écrit : Is this issue needed for next alpha? — Reply to this email directly or view it on GitHub.
Le 6 janv. 2016 à 09:09, Nicolas Lœuillet notifications@github.com a écrit :
— Reply to this email directly or view it on GitHub.
j0k3r
No branches or pull requests
Instead of keeping two differents repositories of site configs, it could be better to contribute to the official site config repo from @fivefilters: https://github.com/fivefilters/ftr-site-config
So we need to extract site configs from wallabag v1 (here: https://github.com/wallabag/wallabag/tree/master/inc/3rdparty/site_config/standard) and merge them in the fivefilters repo.
The text was updated successfully, but these errors were encountered: