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
When a release is made for a resource with a selection of a few completed books, the manifest of the resource contains only the books that are in the release.
There is a bug there that now happens that whatever the manifest file in the new release tag is, it is now also updated into the master branch, this breaks gateway-edit workflow, since the non-released files are now not in the manifest in master and gateway-edit needs them to load the resources.
Master branch has all the books that are in progress as well as completed, so the Manifest also should have the books that are in the master branch.
DOD: Gateway-admin should not update the manifest in the master branch after a release.
The text was updated successfully, but these errors were encountered:
Looks good in v0.9.8 build f37bde8 on develop branch. Scripture and help resources release process works as expected. Release branch manifest has only the published books and the master branch manifest has all the books that are in progress.
When a release is made for a resource with a selection of a few completed books, the manifest of the resource contains only the books that are in the release.
There is a bug there that now happens that whatever the manifest file in the new release tag is, it is now also updated into the master branch, this breaks gateway-edit workflow, since the non-released files are now not in the manifest in master and gateway-edit needs them to load the resources.
Master branch has all the books that are in progress as well as completed, so the Manifest also should have the books that are in the master branch.
DOD: Gateway-admin should not update the manifest in the master branch after a release.
The text was updated successfully, but these errors were encountered: