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

feat: split guidelines #850

Merged
merged 1 commit into from
Feb 29, 2024
Merged

feat: split guidelines #850

merged 1 commit into from
Feb 29, 2024

Conversation

hxtree
Copy link
Owner

@hxtree hxtree commented Feb 29, 2024

No description provided.

@hxtree hxtree enabled auto-merge (squash) February 29, 2024 05:51
@hxtree hxtree disabled auto-merge February 29, 2024 05:52
@hxtree hxtree merged commit e3139d3 into main Feb 29, 2024
8 of 10 checks passed
@hxtree hxtree deleted the feature/split-guidelines branch February 29, 2024 05:52
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
-0.09%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (f1018b1) 2138 1574 73.62%
Head commit (77d3cf1) 2138 (+0) 1572 (-2) 73.53% (-0.09%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#850) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant