Repository navigation
Replies: 2 comments 4 replies
|
If your fork still has the original al-folio Git history, you can check the version from the commits/tags rather than trying to identify it from the current files. From your repository, try: git describe --tags --always If the original al-folio tag is part of your history, this should show something like You can also check which al-folio tags are available with: git tag -l "v*" If you don't have the original tags locally, add the upstream repository and fetch its tags: git remote add upstream https://github.com/alshedivat/al-folio.git Then you can compare your repository's history against the upstream tags to find the closest matching release. I would use the Git history to confirm the version rather than relying on the date the site was created. |
|
Yes. There are several ways to determine which version of al-folio your repository was originally based on, although the exact version may not always be stored explicitly in a single file. The most reliable approach is to check the Git history of your fork. 1. Check the Git historyIf your repository was created by forking git log --oneline --decorate --allYou can also inspect the repository's history on GitHub and look at the earliest commits. If the original al-folio commits are still present in your fork's history, the commit SHA can be compared with the upstream repository. For example: git remote -vIf the upstream repository is configured, you can add it if necessary: git remote add upstream https://github.com/alshedivat/al-folio.git
git fetch upstreamThen you can compare your repository's history with the upstream 2. Look for a version/tag in the repositorySome releases of al-folio correspond to GitHub releases or tags. You can check the tags in the upstream repository: git tagor on GitHub under Releases / Tags. If the commit that your repository was based on corresponds to a particular tag, that tag gives you a good indication of the al-folio version you originally used. 3. Check the repository filesThere isn't necessarily a universal file in every al-folio-based repository that says something like: Depending on when the template was copied and how it was customized, version-related information may instead be visible through files such as However, those files should not be treated as definitive proof of the original template version, because they may have been modified after the repository was created. 4. If the Git history was rewrittenIf the repository was created by copying the files rather than actually forking the upstream repository, or if the Git history was squashed/recreated, determining the exact original version becomes more difficult. In that case, the best method is to compare the files in your repository with historical commits/tags of So, in short: If the original Git history is preserved: compare the earliest commit in your repository with the upstream al-folio commits/tags. If the history is not preserved: compare your current files against historical al-folio releases/tags. There may not be a single file in the fork that explicitly records the exact al-folio version. |
Uh oh!
There was an error while loading. Please reload this page.
How can I tell which version of al-folio did I use as template? Is it written in some file somewhere in the "forked" repo?
I made the website in June 2025, so most likely it is v0.14.6, but I'd like to know for sure, as I plan to update and would like to check change-logs and minimize headaches.
And if it is not recorded in any file - should it be?
Thanks!
All reactions