Indeed, PR's are a useful way to 'package' the interactions and changes to a code base from someone else. It allows to see a condensed view of all that was changed, so it's easier to grasp the intent and methods used. (to eventually accept, or refuse changes until further modifications/fixes)
For personal code base management, not involving any third party, I just pull changes of a branch into some other branch as needed, and push back when it's done. -- Félix On Sunday, October 11, 2020 at 2:53:34 PM UTC-4, Edward K. Ream wrote: > > As I understand it, a PR is required only when attempting to merge a > branch into someone *else's* branch. No need to create an issue and PR > for branches that we own. > > The recent fix in devel for findFirstValidAtLanguageDirective does not, > imo, need the full issue/pr machinery. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/1edd70c7-fd0c-4da5-aa69-0b958ef20ed6o%40googlegroups.com.
