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

Move clone_progress to separate list #2929

Merged
merged 1 commit into from
Oct 19, 2023

Conversation

avlitman
Copy link
Contributor

@avlitman avlitman commented Oct 18, 2023

What this PR does / why we need it:
Since clone_progress metric used for internal purpose only we should not document it in metrics.md or test it in the metrics linter. therefore clone_progress moved to separate list (not used by the doc and linter generators).

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2515
Jira-ticket: https://issues.redhat.com/browse/CNV-33647

Special notes for your reviewer:
This fix was discussed with CDI developer.

Release note:

The "clone_progress" metric has been removed from the project documentation. We have decided to exclude this metric from the documentation as it is intended for internal use only.

@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/M labels Oct 18, 2023
@avlitman avlitman changed the title Move clone_progress t list Move clone_progress to separate list Oct 18, 2023
Since clone_progress metric used for internal purpose only we should not
document it in metrics.md or test it in the metrics linter. therefore
clone_progress moved to separate list (not used by the doc and linter
generators).

Signed-off-by: Aviv Litman <alitman@alitman-thinkpadp1gen4i.tlv.csb>
@avlitman
Copy link
Contributor Author

/retest

@avlitman
Copy link
Contributor Author

Please do not merge this PR before @sradco approves.

@awels
Copy link
Member

awels commented Oct 19, 2023

/hold waiting on @sradco to review

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 19, 2023
@avlitman avlitman requested a review from sradco October 19, 2023 13:47
@sradco
Copy link
Contributor

sradco commented Oct 19, 2023

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 19, 2023
Copy link
Member

@awels awels left a comment

Choose a reason for hiding this comment

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

/approve
/hold cancel

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 19, 2023
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 19, 2023
@kubevirt-bot kubevirt-bot merged commit 71ee847 into kubevirt:main Oct 19, 2023
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

clone_progress metric doesn't meet the metrics naming conventions
4 participants