each branch can be each cog's own individual workspace or a clone of master, whichever is more convenient.
If we're planning on having a publishable branch (master), when merging, we'll need to make sure it conforms with Red cog repos' specifications.
anybody against Github Flow as our workflow more or less? 2-3 👍 before merge to publish? Keep security in mind
We can have the branch structure like this:
master --> Red Cog repo structure github-cog --> individual cog workspaces gsheets-cog --> ..
each branch can be each cog's own individual workspace or a clone of master, whichever is more convenient. If we're planning on having a publishable branch (master), when merging, we'll need to make sure it conforms with Red cog repos' specifications.