💡 Idea
With the latest release of pyansys/actions, the PyMAPDL CI/CD pipeline should get simplified. In addition, these actions introduced the multi-version documentation feature, meaning that we can get rid of the stable and developers doc repositories. The CNAME for the development documentation can also be disabled.
Since PyMAPDL is a mature project with several releases already performed, the migration process may be a bit more complex when talking about multi-version documentation. Therefore, we can coordinate for this task, @germa89 so you are also aware about how everything fits together.
Once setup, everything will work in automated mode, no need to perform more maintenance.
💡 Idea With the latest release of pyansys/actions, the PyMAPDL CI/CD pipeline should get simplified. In addition, these actions introduced the multi-version documentation feature, meaning that we can get rid of the stable and developers doc repositories. The CNAME for the development documentation can also be disabled.
Since PyMAPDL is a mature project with several releases already performed, the migration process may be a bit more complex when talking about multi-version documentation. Therefore, we can coordinate for this task, @germa89 so you are also aware about how everything fits together.
Once setup, everything will work in automated mode, no need to perform more maintenance.