p5.js-website update workflow#4733
Merged
outofambit merged 4 commits intoprocessing:mainfrom Aug 19, 2020
Merged
Conversation
…kienomiya/p5.js into p5.js-website-update-workflow
Member
|
The steps in this file should be automating releasing |
Contributor
|
hey @limzykenneth sorry i should have remembered that file when @yukienomiya and i were first discussing this work. this work in combination with processing/p5.js-website#841 does replace this script (and removes the requirement to run locally), so we can remove it. |
outofambit
approved these changes
Aug 17, 2020
Contributor
outofambit
left a comment
outofambit
left a comment
There was a problem hiding this comment.
will merge tomorrow! last call for comments! :D
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes:
Add a GitHub workflow that gets triggered every time a p5.js release gets published. This workflow will then trigger a second workflow on the p5.js-website repository that will update the p5.js documentation in the website's repository.
This way the data.json file won't need to be manually updated every time there's a new p5.js release.