Make branch feature/dual_kawase its own repo

[eepykate]

It's a fork of picom, not compton, so I feel like that should be in its own repo, which is forked from yshui/picom instead of chjj/compton.

[tryone144]

I can certainly see where you are coming from, but keep in mind that yshui/picom still is a fork of chjj/compton, just like this repo is. And GitHub does not support multiple forks for one user.

However, it might be a good idea to rename and rebase my fork completely against yshui's picom in the future.

[eepykate]

keep in mind that yshui/picom still is a fork of chjj/compton, just like this repo is.

I am aware, I just mean so the subtext below user / project is more accurate to where most of the code is from.

And GitHub does not support multiple forks for one user.

Do you mean multiple forks (or forks of forks) of the same project? Or total forks?

Edit: Ahhh I see what you mean now. If I try forking compton and picom it only makes one repository.

[tryone144]

Since the default branch is still based on the original compton, I'll keep the name for the time being. Once the feature branch is "backward-compatible" (e.g. the name changed from kawase to dual_kawase), I'll make it the default and rebase/rename it to yshui' picom to correctly reflect the codebase.