Run in repos without a trunk.yaml

[gewenyu99]

Originally by Sam Lijin in Canny:

This has come up in a few contexts

• polyrepo setups where folks want just a single trunk.yaml across all of them
• folks who want a low-overhead setup for personal development

If this is you, please comment describing your use case so that if/when we get around to this, we can consider it when designing the implementation!

[gewenyu99]

Some situations described by Trailstrider:

I've got multiple scenarios where this applies.

The polyrepo approach definitely applies for me, and since this is a VS Code extension, I shouldn't even need a yaml file to configure, I should be able to have a native VS Code Extension configuration. That said, a specific repo should be able to provide a different configuration that my polyrepo generic. BTW, VS Code has a natural way to handle this, with the user/workspace settings.

Personal development variants that come up

1. Just working on a quick script because the task is a bit more complicated and as-you-go linting from things like ShellCheck would make that work more efficient.
2. Adopting code from a repo when there is no intent to merge/commit changes back into the repo (mainly because you're not a developer of the repo you just grabbed from github)
3. Someone else sends you some code, you need it, but there is awkward syntax present and a linter can help demystify some things, or even show you issues you could avoid (I've dealt with this several times this week already!)