Skip to content

Conversation

palkerecsenyi
Copy link
Member

Closes #188


  • Updated the view handlers and the Jinja templates to accommodate the new generic structure. The view handlers needed only relatively small changes, but the Jinja templates had to have all references to 'GitHub', the GitHub logo, and GitHub URLs replaced with provider-specific references. The 'vocabulary' defined in the
    RepositoryServiceProviderFactory specifies the terminology that should be used for a given VCS, including the name/icon but also the word for 'repository' which is 'project' for GitLab.

  • The ext.py file is also changed here to reflect the dynamic submenu entries depending on the VCS providers registered in the config.

  • This commit on its own is UNRELEASABLE. We will merge multiple commits related to the VCS upgrade into the vcs-staging branch and then merge them all into master once we have a fully release-ready prototype. At that point, we will create a squash commit.

@palkerecsenyi palkerecsenyi linked an issue Sep 25, 2025 that may be closed by this pull request
13 tasks
* Updated the view handlers and the Jinja templates to accommodate the
new generic structure. The view handlers needed only relatively small
changes, but the Jinja templates had to have all references to 'GitHub',
the GitHub logo, and GitHub URLs replaced with provider-specific
references. The 'vocabulary' defined in the
`RepositoryServiceProviderFactory` specifies the terminology that should
be used for a given VCS, including the name/icon but also the word for
'repository' which is 'project' for GitLab.

* The `ext.py` file is also changed here to reflect the dynamic submenu
entries depending on the VCS providers registered in the config.

* This commit on its own is UNRELEASABLE. We will merge multiple commits
related to the VCS upgrade into the `vcs-staging` branch and then merge
them all into `master` once we have a fully release-ready prototype. At
that point, we will create a squash commit.
* We are now distributing this module as an optional dependency rather
than pre-bundled with InvenioRDM. So the new way of
activating/deactivating the module is installing/uninstalling it.

* Also, the default value for `VCS_PROVIDERS` is an empty list, so
nothing would be rendered in the UI menu anyway.
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

Successfully merging this pull request may close these issues.

Make invenio-github support other VCS providers

1 participant