Conversation
|
--(need to fix tests first)-- |
| @@ -2,1043 +2,854 @@ | |||
| # yarn lockfile v1 | |||
There was a problem hiding this comment.
Can I migrate this thing to latest Yarn? Pretty plz
| import issueWithParents from "./fixtures/issueWithParents.json"; | ||
| import { describe, expect, test, beforeEach } from 'vitest' |
There was a problem hiding this comment.
Can I also add a formatter? (noticed the ' and " quotes being used :D)
| uses: actions/setup-node@v2 | ||
| with: | ||
| node-version: '16' | ||
| node-version: '22' |
There was a problem hiding this comment.
Slightly better:
| node-version: '22' | |
| node-version-file: '.node-version' |
And put 22.15.0 in .node-version in repo root
There was a problem hiding this comment.
hm, can we use it in package.json too?
There was a problem hiding this comment.
Tools like fnm can read the engines field from package.json (fun fact, I added support for it in Schniz/fnm#839) but setup-node cannot.
|
@amitdahan I plan to add one more automation that will hopefully help us use subissues everywhere and migrate from task lists. Let's discuss maintanence after that? |
LGTM |
2 participants
this is a prerequisite for a next automation to improve working with subissues within projects
using beta is fine-ish as it's mostly about new typings and they are close to releasing it