Skip to content

chore: split codecov to collect and upload workflows#34451

Merged
mergify[bot] merged 3 commits intoaws:mainfrom
QuantumNeuralCoder:codecov-split
May 13, 2025
Merged

chore: split codecov to collect and upload workflows#34451
mergify[bot] merged 3 commits intoaws:mainfrom
QuantumNeuralCoder:codecov-split

Conversation

@QuantumNeuralCoder
Copy link
Copy Markdown
Contributor

Issue # (if applicable)

same as
#34247
#34211

Closes #.

Reason for this change

Description of changes

Describe any new or updated permissions being added

Codecov is split into collect with lesser permissions and upload with escalated permissions.

Description of how you validated changes

Checklist


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@aws-cdk-automation aws-cdk-automation requested a review from a team May 13, 2025 21:08
@github-actions github-actions bot added the p2 label May 13, 2025
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label May 13, 2025
name: coverage-artifacts
path: |
packages/aws-cdk-lib/coverage/cobertura-coverage.xml
pr/NR
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: For my understanding what is the use of sending the PR number? In the another workflow i couldn't see any reference to the PR number being used.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

in case we wanted to use it. let me remove.

name: Codecov Collect

on:
pull_request:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Q: should we need this workflow to be triggered for all branch? or can we trigger only for the main branch?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

all branches no. At least I follow a branch per feature on my fork strategy.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would like to understand the reason behind separating as two different worklows for codecov instead of a single workflow?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Separately pinging you.

- name: Upload Coverage and PR Info
uses: actions/upload-artifact@v4
with:
name: coverage-artifacts
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we consider naming the artificat based on PR number or commit id instead of a static name?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

i believe its just gonna be interim in the env of the PR itself. lmk

@godwingrs22 godwingrs22 self-assigned this May 13, 2025
@aws-cdk-automation aws-cdk-automation added the pr/needs-maintainer-review This PR needs a review from a Core Team Member label May 13, 2025
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented May 13, 2025

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation aws-cdk-automation removed the pr/needs-maintainer-review This PR needs a review from a Core Team Member label May 13, 2025
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented May 13, 2025

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 537fcff
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented May 13, 2025

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit 039a3aa into aws:main May 13, 2025
15 of 16 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

contribution/core This is a PR that came from AWS. p2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants