-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove VERSION file in che-docs; keep antora-playbook.yml up to date instead #18864
Comments
So we'd want to update this bit of code: to update I suspect that fixing this issue will also mean that pages like https://www.eclipse.org/che/docs/che-7/end-user-guide/creating-and-configuring-a-new-workspace/ will be up to date (and thus show 7.25 instead of 7.23) |
Jira docs issue https://issues.redhat.com/browse/RHDEVDOCS-2538 |
PR for making playbook current w/ every weekly release: eclipse-che/che-docs#1823 Then PR to trigger the above from a che-operator release (push to master branch): eclipse-che/che-operator#657 Note that with these changes, we'll want to disable the bit of the che-release cico script that triggers changes to che-docs: |
The content of the PR is always false. The master branch contains the documentation for the released version of Che but the bot is always trying to update the file to the next version. Very confusing.
Example erroneous PR: eclipse-che/che-docs#1806
I am not aware of any process in che-docs using the VERSION file. We should probably remove it completely to remove a source of confusion.
The only relevant place to define the Che version should be in https://github.com/eclipse/che-docs/blob/master/antora-playbook.yml
If we want to keep an automated process, please make sure it is setting the released version of Che in
antora-playbook.yml
(as well as the previous version).The text was updated successfully, but these errors were encountered: