Skip to content

🛠 Tooling: Are actions/upload-artifact calls necessary in test*.yml? #1225

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

Closed
3 tasks done
JoshuaKGoldberg opened this issue Jan 9, 2024 · 1 comment · Fixed by #1241
Closed
3 tasks done

🛠 Tooling: Are actions/upload-artifact calls necessary in test*.yml? #1225

JoshuaKGoldberg opened this issue Jan 9, 2024 · 1 comment · Fixed by #1241
Labels
area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this! type: cleanup Tech debt or other code/repository cleanups

Comments

@JoshuaKGoldberg
Copy link
Owner

Bug Report Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have pulled the latest main branch of the repository.
  • I have searched for related issues and found none that matched my issue.

Overview

Right now, the end-to-end migration test snapshot shows that this repo includes actions/upload-artifact in its test.yml despite the template not including that call:

exports[`expected file changes > .github/workflows/test.yml 1`] = `
"--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ ... @@ jobs:
- run: pnpm run test --coverage
- name: Codecov
uses: codecov/codecov-action@v3
- with:
- flags: unit
- - if: always()
- name: Archive code coverage results
- uses: actions/upload-artifact@v4
- with:
- name: code-coverage-report
- path: coverage
name: Test
"
`;

I don't think that uploading is necessary. Let's delete the lines in .github/workflows/test*.yml.

Additional Info

This repo has had a few Codecov changes in the past:

#473 is what mentions the code coverage reports:

For convenience, all coverage reports are stored in GitHub Actions (https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts).

I've never used that convenience. And codecov also has an online viewer.

@JoshuaKGoldberg JoshuaKGoldberg added area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this! type: cleanup Tech debt or other code/repository cleanups labels Jan 9, 2024
@JoshuaKGoldberg JoshuaKGoldberg added this to the General Simplification milestone Jan 9, 2024
JoshuaKGoldberg added a commit that referenced this issue Jan 14, 2024
## PR Checklist

- [x] Addresses an existing open issue: fixes #1225
- [x] That issue was marked as [`status: accepting
prs`](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22)
- [x] Steps in
[CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/.github/CONTRIBUTING.md)
were taken

## Overview

Removes the offending lines.
Copy link

🎉 This is included in version v1.54.0 🎉

The release is available on:

Cheers! 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this! type: cleanup Tech debt or other code/repository cleanups
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant