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

chore: modify code coverage trigger conditions #709

Merged
merged 1 commit into from
Mar 8, 2023
Merged

chore: modify code coverage trigger conditions #709

merged 1 commit into from
Mar 8, 2023

Conversation

chunshao90
Copy link
Contributor

Which issue does this PR close?

Closes #

Rationale for this change

Modifying non-code files does not require running code coverage.

What changes are included in this PR?

Add paths-ignore in code coverage workflow configuration.

    paths-ignore:
      - 'docs/**'
      - 'etc/**'
      - '**.md'
      - '.dockerignore'
      - 'docker/**'

Are there any user-facing changes?

How does this change test

@chunshao90 chunshao90 changed the title chore: modify coverage trigger conditions chore: modify code coverage trigger conditions Mar 8, 2023
ShiKaiWi
ShiKaiWi approved these changes Mar 8, 2023
View reviewed changes
Copy link
Member

@ShiKaiWi ShiKaiWi left a comment

Choose a reason for hiding this comment

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

LGTM

@ShiKaiWi ShiKaiWi added this pull request to the merge queue Mar 8, 2023
Merged via the queue into apache:main with commit 47a3f0b Mar 8, 2023
chunshao90 added a commit to chunshao90/ceresdb that referenced this pull request May 15, 2023
@chunshao90
chore: modify coverage trigger conditions (apache#709)
7a2f5fd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ShiKaiWi ShiKaiWi ShiKaiWi approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@chunshao90 @ShiKaiWi