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

Use CI/hooks to generate Multiversum JSON. #4

Closed
Paradyx opened this issue Apr 10, 2019 · 4 comments
Closed

Use CI/hooks to generate Multiversum JSON. #4

Paradyx opened this issue Apr 10, 2019 · 4 comments
Labels
wontfix This will not be worked on

Comments

@Paradyx
Copy link
Member

Paradyx commented Apr 10, 2019

Webhooks are fun and this would automate some work of the "Multiversum Redaktion"

@sudo42
Copy link
Member

sudo42 commented Apr 10, 2019

This should be possible with a little bit of effort.

Doesn't this belong to the Multiversum repo, rather than this one?
The scripting would likely be done here to import data from github, but should be triggered by a release hook in our Multiversum repository ...

@Paradyx
Copy link
Member Author

Paradyx commented Apr 10, 2019

Yes, or even better, the scripting is done on travis and wie give travis a push key for this repo.

@sudo42
Copy link
Member

sudo42 commented Apr 10, 2019

Sure, we could totally do that!
All required information should be extractable from the yaml file headers.

This would probably be a sub-task or follow-up of RPGLibrarium/multiversum#2

@Tikrass
Copy link

Tikrass commented Apr 20, 2019

Publishing an edition of "Multiversum" automatically based on Github-releases raises the following questions, which have to be addressed first:

  • How do we distinguish between a new release and a redacted version (e.g. hotfixes) ?
  • How do we get structured meta data for releases.json from one repository to another? Do we checkout the repository and parse the YAML-Header?
  • We would need a distinguished handling of post-processed PDF-files.

Since publishing a new edition is an editorial action, it would require human interaction one way or another. Maybe it is a better idea to extend RPGLibrarium/Multiversum by a new deployment script.

@Tikrass Tikrass closed this as completed Apr 20, 2019
@Tikrass Tikrass added the wontfix This will not be worked on label Apr 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants