Who has the right to merge?

[vvvyyynet]

Just helped @addrichmauch to merge his latest PR into main. The PR had been approved by @maehr but not merged and since Addrich's github account does not have the rights to merge (there's no merge-button) he could not proceed.

What is the intended workflow?

• Either everybody should have merge rights
• Or the reviewers should merge directly after approving.

[flicksolutions]

giving everyone merge rights is not so smart i guess... let's go the other route and let the reviewer merge right away after the approval.
okay for you @vvvyyynet and @pdaengeli ?

By the way: I think this shoudn't have been an issue, but a discussion. but it doesn't matter that much.

[vvvyyynet]

@flicksolutions I agree. Let the reviewers merge directly. Oh, and thanks for making me aware of the "Discussion" section. Never used it so far.

[pdaengeli]

I am indifferent. The goal for this kind of thing (institutional/project/profile site that always risk to become outdated quickly) should be self-service, in my view. We should avoid the processes to become less efficient than for the Uni CMS.

That said I don't really know the tool and have no idea in how many ways builds can fail and how graceful problems are handled.

Personally I'd be happy for somebody to set up a placeholder page (e.g. for a project) and I'd just push a markdown file with the contents, but of course I understand that this would work only in the most basic cases.

Converting this to a discussion.