Migrate all Addons PRs to the active 5.2 or future 5.3 branches

Development
1

@GaryGriffin made a good point that several addons PRs are in the wrong branch to be eligible for Merging into the 5.2 branch.

In another conversation, @Nick-Hall has said that the Master branch in gramps-project/addons-source serves no purpose. So, after migrating open PRs in the Master branch, could that branch be removed?

And since the 5.2 registering is greatly expanded, could all the ready-to-merge PRs in the 50 and 51 maintenance branches be migrated to maintenance/gramps52? Should all the stale Work In progress PRs could be migrated to a 53 branch?

5.2 compatibility creates challenges because some Attributes were made valid in all Plugin types and others added that are specific to certain Plugin types. Unfortunately, the 5.2 (and earlier) Registration module is not at ALL fault tolerant of unrecognized Attributes for a plugin type.

The list of branches is a bit cluttered too. It has some personal branches that seem like they could be archived too.

I wondered if there were applicable workflows for these issues. Perplexity gave some interesting responses. But they were a page or two longā€¦ too much to include here.

A prompt for Perplexity.ai for some strategies for cleaning up

In GitHub, what are the best practices for managing and archiving dead branches of code? Iā€™m looking for a workflow that would effectively ā€˜freezeā€™ these branches and remove them from the active branch list, simplifying choices for new contributors. Please provide strategies in a logical order, starting with preservation methods (like tagging or archiving) before discussing deletion. Also, include any automated solutions using GitHub Actions that could help with this process.

a followup prompt someGitHub Actions workflows to move open PRs:

In the ā€œGitHub Actions to automateā€ include a process to migrate open Pull Requests to the active branch.

2

I removed those branches (mine) where the PR was merged. The remaining branches are either tied to a PR that is awaiting merge or a maintenance branch (gramps42, gramps50, gramps51, gramps52) or master.

1 Like
3

A gramps53 addons branch would be more useful for people who are running the master branch of Gramps. We should either remove the master branch or rename it to gramps53.

1 Like
4

Is it viable to migrate PRs between addon-source branches? And then to have the changes syncā€™d into later versions?

Or should all the PRs just be moved into the master branch (after it is renamed for gramps53)?

5

Most pull requests for addons should probably be in the current branch. This branch can then be merged up on a regular basis.

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.