-
Notifications
You must be signed in to change notification settings - Fork 140
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
New workflow for deploying the v3 spec to the site. #874
Conversation
This workflow uses spec-parser and spdx-3-model to build and deploy the v3 spec into the main spec site, alongside the 2.x versions already deployed. It is designed to be triggered by pushes to the development/v3.0 branch, via manual triggers, and via external triggers. The latter can be used to build workflows to cause the spec to be rebuilt on changes to spec-parser or spdx-3-model. Signed-off-by: Jeff Licquia <[email protected]>
Additional notes: The new workflow will add the 3.0 spec to the dropdown on the main spec page (https://spdx.github.io/spdx-spec/). I was able to test the workflow manually on my system, and it successfully added the 3.0 spec alongside the others. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @licquia - I have to admit, I may not be the best reviewer of actions, but it looks good to me.
If no one finds any issues before Tuesday, I'll merge
Thanks Jeff, I'm not qualified to review the workflow, but from the comments, it seems like a good path. I added @iamwillbar to the thread in case he has a chance to take a look. |
No one objected, so I'll go ahead and merge this in |
@licquia - I just got a rather strange error from github actions after merging this. Any thoughts?
|
This workflow uses spec-parser and spdx-3-model to build and deploy the v3 spec into the main spec site, alongside the 2.x versions already deployed.
It is designed to be triggered by pushes to the development/v3.0 branch, via manual triggers, and via external triggers. The latter can be used to build workflows to cause the spec to be rebuilt on changes to spec-parser or spdx-3-model.