Skip to content
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

[Publishing Section] Add instructions to recommit config.yaml after publishing via CI #49

Open
creativedrewy opened this issue Jul 28, 2023 · 0 comments
Assignees

Comments

@creativedrewy
Copy link
Contributor

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.

@creativedrewy creativedrewy self-assigned this Jul 28, 2023
@creativedrewy 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant