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

Manifest in the master branch of resources should not to be effected by a Release. #202

Open
elsylambert opened this issue Oct 1, 2024 · 2 comments
Assignees
Labels
bug Something isn't working QA/Passed

Comments

@elsylambert
Copy link

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.

@elsylambert
Copy link
Author

Screenshot 2024-10-08 at 9 21 58 AM Error while releasing en_gst for the first time.

@elsylambert
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working QA/Passed
Projects
None yet
Development

No branches or pull requests

2 participants