Conversation
Signed-off-by: Logan McAnsh <logan@mcan.sh>
| echo "dirty working directory..." | ||
| git add . | ||
| git commit -m "dirty working directory..." |
There was a problem hiding this comment.
Why is there a dirty working directory? What steps trigger file changes?
There was a problem hiding this comment.
great question, that i'd love to have an answer for!
the only files that change during the workflow are package.jsons after running our version script which are immediately committed, and that's done after this check 🤷
in my test repo i was getting a changed package-lock.json, but not sure what the dirtiness is here.
might be fine to leave the commit for a day and see if we can remove it tomorrow after we know what changed?
|
🤖 Hello there, We just published version Thanks! |
(cherry picked from commit 8c071d7)
(cherry picked from commit 8c071d7)
update nightly releases to use version.js script
I'm not sure why we're getting a "dirty" working directory though.. perhaps we just
git commit -m "idk man"Signed-off-by: Logan McAnsh logan@mcan.sh
Closes: #