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

Finalize deployment to gh-pages #11

Closed
3 tasks done
dalito opened this issue Mar 13, 2023 · 1 comment · Fixed by #29
Closed
3 tasks done

Finalize deployment to gh-pages #11

dalito opened this issue Mar 13, 2023 · 1 comment · Fixed by #29
Assignees
Labels
enhancement Request for changing or improving existing features

Comments

@dalito
Copy link
Member

dalito commented Mar 13, 2023

  • describe where to find the xlsx-file that matches the current SKOS/turtle-vocabulary version (see README.md)
  • describe where to find the pyLODE-generated HTML-documentation for the current vocabulary version (see README.md)
  • construct url with version for formerly released versions of the vocabulary. Whenever a new version is tagged the deployment should use the version in the url. This requires another pipeline triggered by a new tag on main.
@dalito dalito self-assigned this Jun 29, 2023
@dalito dalito added the enhancement Request for changing or improving existing features label Jul 5, 2023
@dalito
Copy link
Member Author

dalito commented Aug 16, 2023

A solution will be possible with the next minor release 0.7.0 of voc4cat-tool & some pipeline-updates here.

The gh-pages branch will have the following structure:

dev/
  vocab1/
    0000001.ttl
    0000002.ttl
    ...
    index.html (pylode docs)
  vocab1.ttl
  vocab1.xlsx

  vocab2/
    ... (as in vocab1)
  vocab2.ttl
  vocab2.xlsx

  ... (more vocabularies)

latest/  (latest release)
  ... (same sub structure as dev)

v2023-08-14/  (latest release)
  ... (same sub structure as dev)

v2023-08-10/  (2nd latest release)
  ... (same sub structure as dev)

... (older released versions)

For a new release, latest will be overwirtten with the new release. In addition a copy is written to a folder which is named as the release-tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Request for changing or improving existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant