u/paul_h

I'd previously used "finalise and submit" as way of getting Jules to stop making changes and instead make a PR branch for me to consume. I've typed it in three times to a Jules job over 24 hours now and Jules is still making changes as if I had not given it this repeat instruction. I can see others talk of finalize and submit.

Jules has been working for a week on one experimental thing for me - very slowly. It has now gone off track with a few compounded wrong decisions. I want to get the PR back to GitHub then look at the whole thing in my IDE. Maybe even get another LLM to have a look and give insights.

I think there's an alterate workflow: me using the "download zip" button and over the next 30 to 60 mins that Jules prepares that zip of sources. I could then get a command-line LLM to reapply that all to a branch locally and do the commit. Thereafter I have the diffs I want to for posterity.

I'd rather get Jules to make the PR, but I'm lacking the magic phrase. Anyone know that phrase?

https://www.myamericannurse.com/safe-harbor-laws-protecting-nurses-and-patients/ And may other articles.

Hypothetical USA: an R.N. in a unit on shift gets (say) 10 patients needing involved care concurrently, they then get their 11th pt and invoke safe harbo(u)r protections. That unit could be A&E or ICU, or any other where the nurse to patient ratio is discussed.

Such invocation stops the the Board of Nursing (BON) from later coming after your R.N. credentials if something goes wrong due to the staffing ratio. It doesn't shift $$$ liabilities, though that's a popular miscoception, and it would be great if it did.

UK/NHS: Nursing and Midwifery Council (NMC) has a "Duty to Escalate" code - how often does that happen around ratios, and does management calmly accept it when it happens or whisper in ears to get it undone somehow?

Getting Jules to finalise and submit - how?