-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
more strict php requirement #314
Conversation
I think maybe the better idea would be to commit the documentation files that you want to use, otherwise a new personn won't be able to work on the branch 1.x since they won't have the same doc than you and won't generate the same files. Since the github project of the php doc doesn't use tag, you cannot load the specific version that you want, so you need to commit everything. The cleaner way would be to commit you doc files in separates project and then just update the script update.sh to pull from theses projects |
@Kharhamel PR #292 introduced git submodules for the doc files, pinned to a certain commit hash. So in theory, everyone should get the exact same docs (that specific commit hash) |
Hi @dbrekelmans, I've tested branch
I'm trying, but locally I don't know how to reproduce the error. It seems that the step "Check out submodules" was skipped (maybe already cached?) but then the test can't some file:
Maybe the action don't manage correctly the submodules cache? Hi @Kharhamel, as said by @dbrekelmans git submodules are pinned to a certain commit hash, so everyone (including CI) can use exactly the same version. |
@dbrekelmans try using this step on actions: - name: Checkout repository and submodules
uses: actions/checkout@v2
with:
submodules: recursive Instead of steps "Checkout" and "Check out submodules" or replace your |
The CI workflow use a cache (https://github.com/actions/cache) for the documentation file which may be reused between master and 1.x. It would probably be easier to just remove the caching step on 1.x |
Hi @Kharhamel, any news about the solutions that I've suggested here? |
I think this one is obsolete |
No description provided.