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).
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.
Thanks for asking the question, this will be helpful for lots of us.
--
- Shane
Member
The Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
