> On Nov 15, 2024, at 12:26 PM, Shane Curcuru <a...@shanecurcuru.org> wrote: > > Rich Bowen wrote on 11/15/24 11:50 AM: >> Hi, folks, >> I have a question regarding recommended workflow. Is it people’s preference >> that I work directly in preview/* branches on the main repo, for website >> changes, so that we always have a preview of ongoing work? I have been >> creating branches on my own fork, which inserts additional steps here, but >> keeps my work separate from the “official” repo. > > I've long wondered what the best practice for various ASF repos is, so it'd > be great to have clear docs that explain it for ComDev. In particular, I'm > hoping whatever we document supports GitHub Desktop or website users (i.e. > not needing to know anything about git).
So, this question is *specifically* for the comdev-site repo, which is (obviously) a website, not code. So I don’t necessarily expect advice for this repo to be generic for all ASF repos, since there are very different requirements. > >> Q2 is whether those branches should be deleted once they are merged? > > The general advice I've seen is yes, delete after merge; git makes all that > stuff cheap to do/recreate if needed. Unless you're someone regularly adding > new work to the same place, I suppose, and it's easier for you to update your > own branch and then keep working. Cool. In that case, we have a *ton* of cleanup that could be done on our repo. And I expect that this would result in some associated savings on the *.staging.apache.org <http://staging.apache.org/> server — Rich Bowen rbo...@rcbowen.com
