workflow about stylelint

[jeddy3]

Sounds good to me!

[MoOx]

lgtm too !

I also propose:

• this github labels: https://github.com/cssnext/cssnext/labels
• pr all the times with at least 2 go from some "core" members (well we are not too many for now :D)
• a feature: a pr + minor bump (if > 0.x, minor as patch)
• a fix: pr, automerged if needed
• release: proper tag + changelog + github release (fyi, I use this to https://github.com/MoOx/setup/blob/master/functions/npmpublish, kind of oldschool but works like a charm. I generate github release from changelog using this https://github.com/MoOx/setup/blob/master/bin/npmrelease (called from npmpublish)

[davidtheclark]

Ok. But @MoOx would you be ok with batching new features more in these early stages?

I have a question, too: I don't know if I've messed with your intended Git workflow already. I see that you created a 0.1.0 branch. How do you want the Git workflow to proceed? (What I'm used to is different, I think, because it's just using master to represent the latest accepted changes, creating feature branches that merge back into master, and tagging releases from master.)

[MoOx]

Yeah sure you can push push push :)

I don't really care about branch name. I prefer relying on github labels to sort stuff.
You workflow is totally fine:

• master is only stable (released most of the time)
• we use branch for feature or fix or whatever
• I tag from master using package.json version (I bump version "by hand" when I edit the changelog)

When I push stuff that will not be released asap for some reason, I add edit the changelog prefixed by "HEAD" or "Unreleased".

We can go as you want, we can adjust if we got trouble later ;)
What you are doing is great (start to work on this). Really nice to see someone on this project !!

[jeddy3]

And I'm more than happy to follow your two leads on things like issues labels, git workflow and releases.

[tunnckoCore]

It seems you dont know that https://github.com/tj/git-extras

[MoOx]

@tunnckoCore very interesting. Thanks for sharing.

[MoOx]

@tunnckoCore I just take a quick look to git-extras, and I prefer to fill changelog on each commit with accurate ordered messages (breaking changes first etc). For release I also prefer my simple and stupid script since this one include tests from fresh modules and handle automatic github release from changelog (which is not handled by git extras). It's still interesting tho.

[davidtheclark]

I think this discussion has had its start and we'll figure out what works more precisely, if necessary, as we build more.