Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ensure DCO Workflow Check #834

Closed
2 tasks done
peternied opened this issue Sep 30, 2021 · 0 comments
Closed
2 tasks done

Ensure DCO Workflow Check #834

peternied opened this issue Sep 30, 2021 · 0 comments
Labels
enhancement New feature or request v1.1.0

Comments

@peternied
Copy link
Member

peternied commented Sep 30, 2021 •
edited
Loading

Coming from opensearch-project/project-meta#17

A Developer Certificate of Origin is required on commits in the OpenSearch-Project.

See doc.yml for an example workflow. Ensure CONTRIBUTING.md to has a section on the DCO per the project template.

  • DCO Check Workflow
  • CONTRIBUTING.md DCO Section
@peternied peternied added the enhancement New feature or request label Sep 30, 2021
@peternied peternied mentioned this issue Sep 30, 2021
Closed
47 tasks
@peternied peternied changed the title Ensure Ensure DCO Workflow Check Sep 30, 2021
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Oct 5, 2021
@ananzh
Ensure DCO Workflow Check
ba96f57 
Issue Resolved:
opensearch-project#834

Signed-off-by: Anan Zhuang <ananzh@amazon.com>
@ananzh ananzh mentioned this issue Oct 5, 2021
Merged
5 tasks
@ananzh ananzh closed this as completed in b377f2e Oct 5, 2021
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Oct 5, 2021
@ananzh
[1.1] Ensure DCO Workflow Check
f30030c 
Issue Resolved:
opensearch-project#834

Backport PR:
opensearch-project#841

Signed-off-by: Anan Zhuang <ananzh@amazon.com>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Oct 5, 2021
@ananzh
[1.x] Ensure DCO Workflow Check
e7397db 
Issue Resolved:
opensearch-project#834

Backport PR:
opensearch-project#841

Signed-off-by: Anan Zhuang <ananzh@amazon.com>
This was referenced Oct 5, 2021
Merged
Merged
ananzh added a commit that referenced this issue Oct 5, 2021
@ananzh
[1.x] Ensure DCO Workflow Check (#847)
3c38a38 
Issue Resolved:
#834

Backport PR:
#841

Signed-off-by: Anan Zhuang <ananzh@amazon.com>
ananzh added a commit that referenced this issue Oct 5, 2021
@ananzh
[1.1] Ensure DCO Workflow Check (#846)
3e6d39e 
Issue Resolved:
#834

Backport PR:
#841

Signed-off-by: Anan Zhuang <ananzh@amazon.com>
AMoo-Miki pushed a commit to AMoo-Miki/OpenSearch-Dashboards that referenced this issue Feb 10, 2022
@nickofthyme
feat: debug state flag added to chart status (opensearch-project#834)
f3aba25
AMoo-Miki pushed a commit to AMoo-Miki/OpenSearch-Dashboards that referenced this issue Feb 10, 2022
@semantic-release-bot
chore(release): 23.0.0 [skip ci]
b318e5f 
# [23.0.0](elastic/elastic-charts@v22.0.0...v23.0.0) (2020-09-30)

### Bug Fixes

* render continuous line/area between non-adjacent points ([opensearch-project#833](elastic/elastic-charts#833)) ([5222c40](elastic/elastic-charts@5222c40)), closes [opensearch-project#825](elastic/elastic-charts#825)

### Features

* debug state flag added to chart status ([opensearch-project#834](elastic/elastic-charts#834)) ([f3aba25](elastic/elastic-charts@f3aba25))
* expose datum as part of GeometryValue ([opensearch-project#822](elastic/elastic-charts#822)) ([e582bd6](elastic/elastic-charts@e582bd6))

### BREAKING CHANGES

* when rendering non-stacked line/area charts with a continuous x scale and no fit function,
the line/area between non-consecutive data points will be rendered as a continuous line/area without adding an uncertain dashed line/ semi-transparent area that connects the two, non-adjacent, points.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request v1.1.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peternied @tmarkley