Build and deploy the v3.0 spec on changes. #888
Merged
Conversation
This file contains 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
goneall
reviewed
Feb 26, 2024
|
@licquia I just noticed the CI wasn't passing the DCO - if you could fix or add a comment that it is signed off by you. |
added 7 commits
February 26, 2024 21:35
Signed-off-by: Jeff Licquia <[email protected]>
Signed-off-by: Jeff Licquia <[email protected]>
Signed-off-by: Jeff Licquia <[email protected]>
Signed-off-by: Jeff Licquia <[email protected]>
Signed-off-by: Jeff Licquia <[email protected]>
Signed-off-by: Jeff Licquia <[email protected]>
Signed-off-by: Jeff Licquia <[email protected]>
licquia
force-pushed
the
development/v3.0
branch
from
1112e07
to
54907a6
Compare
|
Rebased to remove some other commits that have already been merged. Should be good now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rebuild the spec using GitHub Actions on changes to the 3.0 branch, and deploy to the spec website with a new version (v3.0, aliased to v3-draft). The build can also be triggered from external repository changes and manually.