Versioning CSL styles

It’s a different problem. git clients and applications generally expect there to be a ‘master’ branch. Although there is no necessary special status of “master”, I’ve had problems with some git clients setting up repos that didn’t have a master branch.

We buy and large aren’t serving styles directly through GitHub anyway, are we? They are served through the Zotero Style Repository. We are also transitioning to serving the schema and spec through resources.citationstyles.org. Is there need to orient the styles repo around serving the styles, rather than around development?

There shouldn’t be. To echo discussions in two recent threads, 1) filenames on GitHub are not ids and should be able to be changed at will without breaking clients and 2) GitHub raw links can’t be redirected. Clients should bundle specific style versions and/or pull from a repository that serves styles via id (and perhaps can handle conditional logic to serve different versions of styles to different clients, perform redirects based on previous renamed-styles.json entries, etc.).

1 Like