-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update all repos to move release data to catalog-info.yaml #1121
Comments
@irtazaakram When you switch a repo over to catalog-info, make sure that you set the release branch value to whatever it was in openedx.yaml, usually "master" or "main". Setting it to null removes it from the release. |
@feanil is there need to add release data like openedx.org/release: "master" in catalog.yaml file, when openedx.yaml don't have release tag. One particular example is https://github.com/openedx/edx-ora2/blob/master/openedx.yaml |
@salman2013 If there is no release data in openedx.yaml, then that means that the repository shouldn't be tagged (most likely because it is a package, which is installed into a tagged repository). The catalog-info file should either have |
Note: Just to keep track i am adding this list in the comment. As per my search following list of repositories does not have
|
@salman2013 of those, you only needto prioritize the repos that have an |
In some cases, the file will already exist and need to be updated, and in others, it won't exist and will need to be created. Other fields can be left blank for now in the case of creation.
Don't remove the old
openedx.yaml
file in this step, we will do that as future work in a different ticket.The text was updated successfully, but these errors were encountered: