Closed silverhook closed 5 years ago
@justinmayer can you have a look on this? Thanks!
Would be easier to do so if there were clearer instructions as to the exact perceived steps required to close this issue.
I haven’t done this before, but I would guess that in the .gitmodules
file Elegant’s block should now say:
[submodule "elegant"]
path = elegant
url = https://github.com/Pelican-Elegant/elegant.git
@talha131, can you provide more info on how this is to be done? You have done this before.
I'll submit PR for it Pablo Iranzo Gómez
GnuPG: 0x5BD8E1E4 Web: https://iranzo.github.io || https://citellus.org
El sáb., 29 dic. 2018 a las 0:34, Matija Šuklje (notifications@github.com) escribió:
I haven’t done this before, but I would guess that in the .gitmodules file Elegant’s block should now say:
[submodule "elegant"]
path = elegant url = https://github.com/Pelican-Elegant/elegant.git
@talha131 https://github.com/talha131, can you provide more info on how this is to be done? You have done this before.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/getpelican/pelican-themes/issues/623#issuecomment-450443336, or mute the thread https://github.com/notifications/unsubscribe-auth/AATEjyNyx9my6uMDx-aQWRyCHwXc6kUNks5u9qqKgaJpZM4Y5E0e .
@silverhook You were right. @iranzo PR has fixed the issue. It just needs to be merged.
Recently Elegant grew into a community-based effort and to reflect that, changed its (GitHub) organisation as well as governance (see https://github.com/Pelican-Elegant/elegant/issues/173 for more info).
As part of that the main repository has changed from: https://github.com/talha131/pelican-elegant/ to: https://github.com/Pelican-Elegant/elegant
The redirect seems to be working, but for the future it would be good to point to the right repository.
(teaser: we’re working on releasing 2.0 soon, and plans for 3.0 are already under discussion)