Skip to content

Add code coverage comment on the PR#5367

Open
rbans96 wants to merge 4 commits intomainfrom
personal/ribans/alert-if-code-coverage-down
Open

Add code coverage comment on the PR#5367
rbans96 wants to merge 4 commits intomainfrom
personal/ribans/alert-if-code-coverage-down

Conversation

@rbans96
Copy link
Contributor

@rbans96 rbans96 commented Feb 3, 2026

Description

Add code coverage comment on the PR

Related issues

Addresses 182456

Testing

Describe how this change was tested.

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@rbans96 rbans96 added this to the CY25Q3/2Wk07 milestone Feb 3, 2026
@rbans96 rbans96 requested a review from a team as a code owner February 3, 2026 22:44
@rbans96 rbans96 added Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs No-PaaS-breaking-change No-ADR ADR not needed Build labels Feb 3, 2026
@rbans96
Copy link
Contributor Author

rbans96 commented Feb 4, 2026

/azp run

@azure-pipelines
Copy link

azure-pipelines bot commented Feb 4, 2026

Azure Pipelines successfully started running 1 pipeline(s).

@rbans96
Add workflow_dispatch and expand trigger paths for coverage comparison
c73dbeb 
- Add workflow_dispatch for manual triggering from Actions tab
- Trigger on build/**/*.yml changes (pipeline configs)
- Trigger on .github/workflows/** changes
- Trigger on CodeCoverage.runsettings changes
@rbans96
Move coverage comparison to Azure DevOps pipeline
d10fc0c 
- Remove GitHub Actions workflow (only ran unit tests, not full coverage)
- Add coverage comparison to aggregate-coverage.yml that:
  - Fetches main branch's latest successful build coverage artifact
  - Compares PR coverage against main baseline
  - Posts comment on GitHub PR with comparison table
- Requires GitHubPAT pipeline variable for PR comments
@rbans96
Copy link
Contributor Author

rbans96 commented Feb 4, 2026

/azp run

@azure-pipelines
Copy link

azure-pipelines bot commented Feb 4, 2026

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs Build No-ADR ADR not needed No-PaaS-breaking-change

Projects

None yet

Milestone

CY25Q3/2Wk07

Development

Successfully merging this pull request may close these issues.

1 participant

@rbans96