Case study for ZCITC Streamlining Urban Parking with KubeEdge (ENG) #659
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
Signed-off-by: GitHub <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubeedge-bot
added
the
size/L
wbc6080
reviewed
Jan 10, 2025
There was a problem hiding this comment.
You can use this link to view the display results on the front end of the website to adjust the formatting issues.
https://deploy-preview-659--kubeedge.netlify.app/case-studies/zcitc/
Signed-off-by: GitHub <[email protected]>
wbc6080
reviewed
Jan 10, 2025
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.
Which issue(s) this PR fixes:
Fixes #
I was going through the case studies, I saw we have case studies in Mandrine for this blog but not for English, so I added one.
What is the current behavior? (You can also link to an open issue here)
We don't have an English blog for this case study
What is the new behavior (if this is a feature change)?
I have added one
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: