Description
At the moment website updates - especially for doc - pages are done with each push of main branch.
At that point, the Github release nor PSGallery release reflect this.
Steps to Reproduce
- push to
main branch
- see action for website running and deploying change
Expected Behavior
Changes in code shall only be online in docs, when released.
Additional Context
Not sure if website build should be restricted (general page changes should still be available on main push, only changes in docs not).
Maybe using docusaurus versioning features (e.g. as in Maester.dev)?
Description
At the moment website updates - especially for doc - pages are done with each push of
mainbranch.At that point, the Github release nor PSGallery release reflect this.
Steps to Reproduce
mainbranchExpected Behavior
Changes in code shall only be online in docs, when released.
Additional Context
Not sure if website build should be restricted (general page changes should still be available on
mainpush, only changes indocsnot).Maybe using docusaurus versioning features (e.g. as in Maester.dev)?