Meta tags:
author=David;

Headings (most frequently used words):

reverts, comments, add, your, thoughts, cancel, reply,

Text of the page (most frequently used words):
the (48), svn (15), that (14), wordpress (13), and (13), ticket (12), commit (11), this (10), #revert (9), have (9), use (8), then (8), run (8), for (8), core (7), diff (7), name (5), add (5), can (5), code (5), trac (5), files (5), are (4), merge (4), bit (4), thing (4), something (4), workflows (4), all (4), function (4), patch (4), patches (4), fork (4), development (3), find (3), how (3), committing (3), reverts (3), specific (3), one (3), actually (3), else (3), time (3), only (3), few (3), make (3), with (3), trunk (3), workspace (3), end (3), number (3), git (3), type (3), grunt (3), patch_index (3), also (3), pull (3), github (3), com (3), develop (3), xxxxx (3), dream (2), encode (2), custom (2), email (2), your (2), web (2), about (2), david (2), handle (2), tortoise (2), makes (2), there (2), context (2), menu (2), which (2), you (2), want (2), even (2), next (2), click (2), just (2), any (2), mbp (2), sergey (2), clean (2), contributor (2), day (2), into (2), wordcamp (2), committed (2), some (2), once (2), post (2), open (2), prs (2), were (2), actual (2), windows (2), relevant (2), branch (2), tortoisesvn (2), current (2), file (2), sure (2), every (2), different (2), other (2), rely (2), tests (2), push (2), npm (2), test (2), svn_clean (2), orig (2), delete (2), rej (2), when (2), script (2), like (2), out (2), read (2), index (2), first (2), branches (2), alias (2), many (2), change (2), sync (2), upstream (2), jorbin (2), had (2), our (2), along (2), copyright, 2016, 2026, subscribe, posts, shop, commerce, warehouse, operations, woocommerce, maintenance, support, upwork, say, hello, website, comment, required, fields, marked, address, will, not, published, cancel, reply, thoughts, pingback, jonathan, desrosiers, comments, tags, developer, pretty, easy, pops, asking, revision, browse, recent, commits, check, box, proceed, complete, through, process, above, normally, didn, well, after, hesitant, stuff, eventually, comes, rescue, mess, someone, reverted, good, most, means, learning, rethink, approach, give, more, settle, before, making, major, release, during, same, bad, needed, stupid, decided, bring, tried, cornerstone, recommended, desrosj, watch, gha, completion, close, attached, wait, inevitably, fix, screwed, finally, admin, manually, props, folks, missed, explorer, right, folder, opens, shows, list, modified, directory, compare, base, each, looking, what, expect, select, forgetting, new, friggin, edit, message, press, button, instead, command, line, unit, former, against, been, annotated, group, faster, than, form, waiting, again, e2e, php, small, both, left, doesn, apply, cleanly, while, sorta, taking, trash, svn_make_core_patch, echo, supplied, exiting, couple, aliases, come, handy, interactive, pipe, multiple, already, honestly, very, rarely, anymore, since, going, back, checked, tag, etc, working, space, heavily, terminal, https, xxxx, useful, ways, least, setup, easier, archaeology, lines, backtrace, history, secondly, easily, dedicated, actions, updated, validate, where, added, here, bash, changes, org, mirror, separate, directories, workspaces, house, various, areas, vary, purpose, main, two, similar, portland, committers, attendance, quick, meetup, lunch, thursday, everyone, met, person, discuss, anything, anyone, wanted, related, act, mentioned, might, helpful, shared, own, personal, blogs, share, knowledge, tips, tricks, play, photo, credit, andy, fragen, andyfragen, permalink, september, 2024, client, login, contact, blog, updraftplus, backup, exclude, image, thumbnails, dashboard, plugin, stats, acf, object, field, plugins, services,

Text of the page (random words):
how i commit to wordpress core dream encode about services web development plugins wordpress acf post object field type add on wordpress dashboard plugin stats wordpress updraftplus backup exclude image thumbnails blog contact client login david september 25 2024 1 1 permalink photo credit andy fragen andyfragen on x com at wordcamp us in portland or the core committers in attendance had a quick meetup at the end of lunch on thursday to make sure everyone had met in person and to discuss anything anyone wanted related to the act of committing to core jorbin mentioned it might be helpful if we all shared our own committing workflows on our personal blogs to share knowledge along with some tips tricks so i ll play along similar to jorbin i have a few separate directories of different vs code workspaces that house the various areas of core that also vary by purpose the main two relevant to this are git mirror fork github com wordpress wordpress develop svn develop svn wordpress org the git fork is useful to me in many ways first at least in my setup it s a bit easier to do archaeology on lines files to backtrace code history secondly i can easily push a change or many to a dedicated branch in my fork and have all the github actions workflows run on that updated code to validate a change i name my branches something like trac xxxxx where the xxxxx is the current ticket number in trac the only thing i ve added here is a gh sync upstream bash alias to sync my fork to pull in the upstream changes in trunk for the svn workspace i have trunk and all branches going back to 4 1 checked out i only use this workspace to commit revert merge tag etc when working on a trac ticket in this space i rely heavily on grunt patch xxxxx or grunt patch https github com wordpress wordpress develop pull xxxx to pull in patches to commit i ll use svn up in the vs code terminal and i also have a sr alias that is just svn revert r i also have a couple of other aliases function that can come in handy the first is a interactive script to pipe svn diff to a file then name it with the trac ticket number and even add an index if there were multiple patches on that ticket already honestly i very rarely use this anymore since we have gh prs function svn_make_core_patch read p ticket ticket if z ticket then echo no ticket supplied exiting else read p patch index patch_index if z patch_index then svn diff patches ticket patch_index diff else svn diff patches ticket diff fi fi next i have small svn_clean function to clean up both orig and rej files that are left when the grunt patch script doesn t apply a diff cleanly i run this every once in a while sorta like taking out the trash function svn_clean svn revert r find name orig type f delete find name rej type f delete the other thing i rely on in the svn workspace is npm run test php and npm run test e2e to have the unit and end to end tests run i can run the former against a specific ticket number if it s been annotated in the tests or a specific group this can be faster than push to my git form and waiting for all the workflows to run again one thing that s a bit different for me is that i am one of the few on windows i actually use tortoisesvn instead of the command line for the actual svn commit for the actual commit i ll open windows explorer right click on the trunk folder or a relevant branch and use the tortoisesvn context menu to commit this opens the tortoise ui which shows the list of modified files in the current directory i ll use the compare with base on each file i m looking to merge to make sure the diff is what i expect select the files i want to merge and forgetting to do svn add for new files every friggin time edit my commit message then press the button post commit i ll watch a few of the gha workflows run to completion close any open prs that were attached to the trac ticket and then wait for sergey to inevitably fix something i screwed up finally i ll go into the core admin on make and manually add props for folks i missed reverts reverts are a good thing most of the time it means we re learning something that makes us rethink an approach or give something a bit more time to settle before making it into a wordpress major release actually during this same wordcamp s contributor day i committed some bad code then needed to revert stupid me decided to bring my mbp that i have only committed on once so i tried to use cornerstone recommended by desrosj to handle the revert this didn t go well i actually reverted someone else s contributor day commit after that i m a bit hesitant to do any svn stuff on the mbp so sergey eventually comes to the rescue to clean up my mess so how do i normally handle reverts tortoise svn makes this pretty easy there s a revert context menu that pops up asking which revision you want to revert you can even use the ui to browse recent commits check the box next to a specific one then proceed click ok to complete the revert then just go through the commit process above to merge the revert about david web developer tags committing core svn 0 comments pingback how i commit to wordpress core jonathan desrosiers add your thoughts cancel reply your email address will not be published required fields are marked comment name email website δ say hello find me on upwork wordpress custom development wordpress maintenance support woocommerce custom development e commerce warehouse operations shop subscribe to my posts copyright 2016 2026 dream encode