Skip to content

[spec] Process for deploying specs #629

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

Closed
littledan opened this issue Dec 22, 2017 · 2 comments
Closed

[spec] Process for deploying specs #629

littledan opened this issue Dec 22, 2017 · 2 comments

Comments

@littledan
Copy link
Collaborator

littledan commented Dec 22, 2017

Seems like the process for deploying a new version of the specification is that someone with write access will run make deploy in the spec/document folder, which will force-push a version to gh-pages. I'm wondering what we should do now

  • Will someone else (@rossberg ?) install bikeshed and regularly run this script?
  • Should I get permissions to write gh-pages?
  • Should I modify deploy.sh to make PRs as well and ask someone to merge them?
  • Should we switch to auto-deployment with Travis-CI, and give that push permissions?

My intuition is to do the fourth one, but I'm wondering if there's some reason @rossberg decided not to go that way when recently setting up the build scripts.

@rossberg
Copy link
Member

No particular reason that this isn't automatised, sounds like a good idea. We just would need to make sure that commit rights are restricted sufficiently then, so that random persons don't have the ability to mess with the live page.

I think it makes sense to give you wirte permissions. But I'm not an admin myself, so I can't change permissions.

Nit: you shouldn't be running make deploydirectly but rather make publish.

@rossberg rossberg changed the title Process for deploying specs [spec] Process for deploying specs May 3, 2018
@rossberg
Copy link
Member

rossberg commented May 3, 2018

This has been automated.

@rossberg rossberg closed this as completed May 3, 2018
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

No branches or pull requests

2 participants