Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Project Conventions: Merging Pull Requests #2283
I suggest we categorize PRs (either using Github labels or own judgment) into the following types which probably will have different "rules" for merging:
Feel free to edit the description and re-word those or add others which are surely missing.
The criteria for a PR being mergeable might include such this as:
Again, feel free to edit/add to this list.
I guess with the above lists, it's just a matter of attaching the criteria to each type of PR, and then codifying that somewhere like HACKING, the wiki, a new CONTRIBUTING file, or wherever. One way to do this association might be to do some simple polls of the contributors.
As noted on #2178 and many other previous issues/PRs etc actually integrating large changes is difficult.
Starting as a small project Geany has many functionalities integrated in code, and they need to be disintegrated
I am afraid I don't have any new insights, just the same as I have said before, git branches, separate these radical makeovers from the stable version until they are ready to replace it, then release Geany 2.xxx to show its a major change.
And (dare I say it) do a GTK and break some stuff, but with plenty of warning.