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.

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

[CI] Update labels for doc issue creation workflow #1789

Conversation

kavilla
Copy link
Member

@kavilla kavilla commented Jun 23, 2022

Description

Example:
https://github.com/opensearch-project/OpenSearch-Dashboards/runs/7015324767?check_suite_focus=true

If we checkout the run, we can see the run fails with:
Resource not accessible by integration

Which I believe because the documentation label is not available in the doc repo. So instead of
creating a documentation label which seems redudant for a doc repo issue, we should use
dashboards because it exists and makes it more specific for the doc repo maintainers.

Signed-off-by: Kawika Avilla [email protected]

Issues Resolved

n/a

Check List

  • New functionality includes testing.
    • All tests pass
      • yarn test:jest
      • yarn test:jest_integration
      • yarn test:ftr
  • New functionality has been documented.
  • Commits are signed per the DCO using --signoff

Example:
https://github.com/opensearch-project/OpenSearch-Dashboards/runs/7015324767?check_suite_focus=true

If we checkout the run, we can see the run fails with:
`Resource not accessible by integration`

Which I believe because the `documentation` label is not available in the doc repo. So instead of
creating a `documentation` label which seems redudant for a doc repo issue, we should use
`dashboards` because it exists and makes it more specific for the doc repo maintainers.

Issue:
n/a

Signed-off-by: Kawika Avilla <[email protected]>
@kavilla kavilla requested a review from a team as a code owner June 23, 2022 20:55
@kavilla kavilla added the ci label Jun 23, 2022
Copy link
Member

@joshuarrrr joshuarrrr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice fix, thanks!

Copy link
Member

@manasvinibs manasvinibs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codecov-commenter
Copy link

Codecov Report

Merging #1789 (19eb856) into main (d1cfe78) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1789   +/-   ##
=======================================
  Coverage   67.51%   67.51%           
=======================================
  Files        3073     3073           
  Lines       59069    59069           
  Branches     8963     8963           
=======================================
  Hits        39881    39881           
  Misses      17005    17005           
  Partials     2183     2183           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1cfe78...19eb856. Read the comment docs.

@joshuarrrr
Copy link
Member

@kavilla Do CI changes like this need to be backported, or will they work for all PRs once merged to main?

@kavilla
Copy link
Member Author

kavilla commented Jun 23, 2022

@kavilla Do CI changes like this need to be backported, or will they work for all PRs once merged to main?

They should but the original doc issue wasn't added to 2.x so it will be a 3.x thing but it should all work.

@kavilla kavilla merged commit 8b7ed4c into opensearch-project:main Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants