You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if a publisher is using a fully CI-driven approach to dApp publishing, their config.yaml file will be changing with each minted release. If they don't re-commit that back to their version control system, that will cause major errors for subsequent releases.
Add a section to the docs that describes the need for committing config.yaml in CI context so subsequent releases will work.
The text was updated successfully, but these errors were encountered:
creativedrewy
changed the title
[Publishing Docs] Add instructions to recommit config.yaml after publishing via CI
[Publishing Section] Add instructions to recommit config.yaml after publishing via CI
Jul 28, 2023
Right now if a publisher is using a fully CI-driven approach to dApp publishing, their config.yaml file will be changing with each minted release. If they don't re-commit that back to their version control system, that will cause major errors for subsequent releases.
Add a section to the docs that describes the need for committing config.yaml in CI context so subsequent releases will work.
The text was updated successfully, but these errors were encountered: