GitHub Workflows for CODEOWNERS for Spices

[rcalixte]

Currently, CODEOWNERS files require manual updating and are frequently out-of-date.

Latest update pull requests:
linuxmint/cinnamon-spices-applets#4925
linuxmint/cinnamon-spices-desklets#859
linuxmint/cinnamon-spices-extensions#468
linuxmint/cinnamon-spices-themes#753

We can instead create a workflow that will auto-run the codeowners_creator.py script after a commit is merged to master and auto-open pull requests if there is a diff on the CODEOWNERS file. (No action would be taken if there was no change to the CODEOWNERS file.)

[rcalixte]

@schorschii I'm thinking we can include the notification changes here. There are options to improve all elements of the current system. Let's take a diligent approach here.

[rcalixte]

It will be overlooked just the same. (The same is already in the existing documentation and it isn't always observed.) And adding something with the sole purpose of reverting it feels wasteful. I have other obligations but I can certainly try to rush this to tomorrow if that would suffice. 😄

[rcalixte]

I do agree that we can adjust the text portions as well. Let's approach this holistically though.

[schorschii]

I don't think it would be the same. The issue/pr template is always seen by the issue/pr author. Only a minority will read documentation before opening issues/PRs.

Don't rush, please take the necessary time. This is why I suggest a simple adjustment of the template text first.

[schorschii]

When do you plan to update the issue/pr templates @rcalixte ?

[rcalixte]

PRs opened here:
linuxmint/cinnamon-spices-applets#5038
linuxmint/cinnamon-spices-desklets#925
linuxmint/cinnamon-spices-extensions#486
linuxmint/cinnamon-spices-themes#759

This is a first pass at the Issue form/template. Once we get something ready to be merged, we can also create an equivalent for Pull Requests.

I need to spend time to get the automation implemented as the team desires but after that, we should be in the clear here.