Here's how most projects workflow are generally setup: My understanding is that people branch from a development 'head', generally not master, as the master branch is reserved for stable and verified commits that as a whole make a bundle to be published. Then, they ultimately finish their commits on their 'new-feature-x' branch... and pull request to be merged back into dev, or devel depending on the projects nomenclature. Called a 'development branch'.
Masters are reserved for published versions and are fine-tuned to be stable (usualy) by the project owner himself. Exception for small projects where features are added from branches of the master directly and no concept of intermediate level between a publicly shown 'master' branch and 'feature' branches. -- Félix On Saturday, July 11, 2020 at 5:40:56 PM UTC-4, Edward K. Ream wrote: > > On Saturday, July 11, 2020 at 3:52:46 PM UTC-5, Edward K. Ream wrote: > > I just received and rejected PR #1615 >> <https://github.com/leo-editor/leo-editor/pull/1615>. This PR was to be >> applied to 6.0-final-rel. That's not how things work. We don't change >> official releases for any reason. >> > > The author does not appear to have commit access, which is troubling. > However, the default branch is "master", not "devel", so perhaps that > explains the situation. > > It is possible to change the default, but changing it brings up a warning > about unintended consequences. > > I think the default branch really should be "devel", but I want to check > with you all first. > > 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/0933e465-0f4f-4bb4-bfb9-f0c456ebf233o%40googlegroups.com.
