[02:57:04] <MirahezeRelay>	 <elisapoly> I messed up my PRs. Ooops  gonna redo them in a few hours
[03:01:35] <MirahezeRelay>	 <kockaadmiralac> You could do an interactive rebase and drop that commit from the PR
[03:03:47] <MirahezeRelay>	 <pskyechology> lazy me would just copy the 5 lines of change, reset to upstream and do it again
[03:03:52] <MirahezeRelay>	 <kockaadmiralac> [1/6] ```
[03:03:52] <MirahezeRelay>	 <kockaadmiralac> [2/6] git checkout ext-ArticleFeedbackv5-permission
[03:03:53] <MirahezeRelay>	 <kockaadmiralac> [3/6] git rebase -i HEAD~2
[03:03:53] <MirahezeRelay>	 <kockaadmiralac> [4/6] ```Change the first line from `pick` to `drop` ```
[03:03:53] <MirahezeRelay>	 <kockaadmiralac> [5/6] git push --force
[03:03:54] <MirahezeRelay>	 <kockaadmiralac> [6/6] ```
[03:04:07] <MirahezeRelay>	 <kockaadmiralac> I guess lol
[03:04:25] <MirahezeRelay>	 <kockaadmiralac> Interactive rebase is one hell of a drug
[03:24:24] <MirahezeRelay>	 <posix_memalign> [1/2] There are lots of ways to save it.
[03:24:25] <MirahezeRelay>	 <posix_memalign> [2/2] I would probably create another branch with `git switch -c`. Edit out the extraneous change, and then `git commit -a --amend`.
[03:56:13] <MirahezeRelay>	 <zipppee> I'd just send some unpaid ai agent to do it
[03:56:23] <MirahezeRelay>	 <zipppee> I make poorly paid ai agents fix all my merge conflicts
[03:56:31] <MirahezeRelay>	 <zipppee> usually it causes more conflicts but hey ho
[03:56:42] <MirahezeRelay>	 <zipppee> then you send another agent :3
[09:11:14] <MirahezeRelay>	 <thewwrnerdguy, replying to zipppee> the epitome of wisdom
[09:11:46] <MirahezeRelay>	 <thewwrnerdguy> I don't commit to my main branch, I let that one follow upstream
[13:13:12] <MirahezeRelay>	 <ccxtwf, replying to ccxtwf> since this patch (and a few other updates since then, including an update to upgrade Bootstrap) has been merged, can Medik be updated site-wide?