update 3.0.0 manifest file for dashboards-notifications #3092
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
|
Hi @ansjcy , Can you fix the lint error? Needs a new line at the end |
Signed-off-by: Chenyang Ji <[email protected]>
ansjcy
force-pushed
the
update-3.0.0-manifest-file-for-notifications
branch
from
5c7f5d7
to
5330313
Compare
|
@gaiksaya Thanks for noticing! just updated the PR. |
gaiksaya
approved these changes
Jan 12, 2023
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.
Signed-off-by: Chenyang Ji [email protected]
Description
Since we already moved
dashboards-notificationsto its own repo, we need to update the 3.0.0 manifest file as well to reflect the change.Issues Resolved
opensearch-project/dashboards-notifications#4
opensearch-project/notifications#466
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.