A healthy development and main branch?

[pgroot91]

@superdav42 Can we stop committing directly to main so we don't end up with a broken project, and just create an MR and merge it when the tests 🟢 have passed?

The tests are there precisely to prevent us from ending up with a broken product/branch 🔴.

It might also be nice if everyone could follow what's going on and maybe also create tickets for the issues that have been resolved, even if they are minor.

[superdav42]

@pgroot91 I can do this. I was too used to working solo on this project although I usually work on a team. I'm very grateful for your and @JoseVega and @marcusquinn and @vuckro and @tamkendigital 's help!

[tamkendigital]

Hi superdav , I'm ready to be with you , what the plane ?

[superdav42]

Hi superdav , I'm ready to be with you , what the plane ?

I created a 2.4.4 Milestone for some things I want to get in the next release. These are issues that are ready to be worked on. Feel free to assign them to yourself. Of course if you see other areas that need work feel free to start on them too.

[vuckro]

Hi, sorry for the late reply.
I’ve just started learning Git/GitHub recently, so I’m still in the early stages.

If you have any best practices or instructions to improve collaboration (branch workflow, PRs, etc.), or if you see a different way we should collaborate, I’m happy to follow your lead 👍

[superdav42]

Basically we should operate with the GitHub flow. This post explains it well. It's how basically all open source projects on github operate. Main should be stable. Work is done in feature branches until it's complete. Open PR and merge it in.

I do see a need for realtime communication if we could get everyone on the same platform. Using the wordpress.org slack workspace seems like a good place to start https://make.wordpress.org/chat/ Looks like some are already on there. When you get in tell me you screen name and I'll add you to a private chat

[superdav42]

[tamkendigital]

I send now +966