Use GitHub project boards for branching

[ekohl]

Branching is often a complex process where a lot of PRs are made. It's easy to lose track of them and a board can help.

We've been experimenting with this, but it should become part of the procedures so it's repeatable.

One issue already found is that only org admins can make it public. Perhaps this could be included in a setting.

Another option to consider is reusing a board for branching / releasing. At the end of a release you can archive all the done items.

[evgeni]

Would a project template (https://docs.github.com/en/issues/planning-and-tracking-with-projects/managing-your-project/managing-project-templates-in-your-organization) help?

[ekohl]

I debated that. However, you need admin permissions to make a board public.

What I've done now is create https://github.com/orgs/theforeman/projects/21/views/1 which is grouped by release. That way we can simply add a new release once we branch. This still needs to be incorporated into the procedures.