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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃洜 Tooling: Repository might not need to pnpm build || true in lint-knip.yml #1087

Closed
3 tasks done
JoshuaKGoldberg opened this issue Dec 11, 2023 · 1 comment 路 Fixed by #1152
Closed
3 tasks done
Assignees
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

JoshuaKGoldberg commented Dec 11, 2023

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

Thanks to #1048, we see now that this repository has two bits of tooling that are different between its 馃崕 actual files and 馃崒 code templates (see Additional Info below for explanation of the emojis):

I'd added pnpm build || true in lint-knip.yml back in #553. It might have been necessary then, but doesn't seem necessary now? If I rm -rf lib locally then run pnpm lint:knip, nothing fails.

I think this should be a straightforward fix of removing the pnpm build || true. That might fail in PR though, so not marking as good first issue. Maybe, good second issue would be more accurate? Welcoming PRs from anybody who's feeling confident and/or has already completed an issue! 馃檪

Additional Info

This repository is two things:

  • 馃崕 An example of a working TypeScript repository, including builds, Knip, package publishing, and more tooling
  • 馃崒 Code that can set up a new or existing repository using all of that repository tooling

For the most part, the repository's end-to-end test for --mode migration makes sure that the 馃崕 actual files and 馃崒 code templates stay the same. As in, if one changes, the other needs to have the same change as well. But per #546, there are some files that were missed in that test. We're only now able to verify that they're the same as of #1048. That PR is where this discrepancy was discovered.

@JoshuaKGoldberg JoshuaKGoldberg added type: bug Something isn't working :( area: tooling Managing the repository's maintenance status: accepting prs Please, send a pull request to resolve this! labels Dec 11, 2023
@JoshuaKGoldberg JoshuaKGoldberg added type: cleanup Tech debt or other code/repository cleanups and removed type: bug Something isn't working :( labels Dec 11, 2023
@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Dec 30, 2023
JoshuaKGoldberg added a commit that referenced this issue Dec 30, 2023
## PR Checklist

- [x] Addresses an existing open issue: fixes #1087
- [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

Finally makes it so a `pnpm build || exit 0` only happens if `bin` is
specified. This is because:
* `n/no-missing-import` will complain if the referenced `.js` file
doesn't exist
* The only way for that file to exist is to `build`
* But, building failing -especially in migrating an existing repo-
shouldn't prevent the rest of the commands from running
Copy link

馃帀 This is included in version v1.51.2 馃帀

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