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
Currently do-release-tags implements the "binary promotion model", but it could be extended to help users with the "promoting content between repositories" method as well.
The user would simply need to add a remote to their ostree repository:
Not only is this useful for promoting your own content, but can also be used to help automate mirroring and promotion of content from third party repositories (i.e. creating local staging/production of CentOS Atomic images).
The text was updated successfully, but these errors were encountered:
Currently do-release-tags implements the "binary promotion model", but it could be extended to help users with the "promoting content between repositories" method as well.
The user would simply need to add a remote to their ostree repository:
And then when running the do-release-tags script a remote would have to be specified to pull missing commits from. Something like:
Not only is this useful for promoting your own content, but can also be used to help automate mirroring and promotion of content from third party repositories (i.e. creating local staging/production of CentOS Atomic images).
The text was updated successfully, but these errors were encountered: