It is a pretty involved process these days. I will write something up when I get the chance, but after doing it today I am pretty used up. The basic process is:
Merge and update the eslint config packages
Merge in the upstream changes from standard, fix conflicts
Read through all the standard change logs and make sure none of them conflict with the happiness rules, fix what needs to be fixed
Comb through the entire project looking for references to standard and Feross, change them to happiness and Jed
Comment out the tests for standard-packages because we have not created a happiness-packages fork
Run the authors bin script
Run tests, fix if necessary
Submit PR
Merge PR
Publish dep packages
Publish main package
I think that is it, but if we start supporting editor plugins we will have to add those steps. Also, I think there is some of this we can automate or at least git checkout --ours README.md type stuff.
It is a pretty involved process these days. I will write something up when I get the chance, but after doing it today I am pretty used up. The basic process is:
standard-packagesbecause we have not created ahappiness-packagesforkI think that is it, but if we start supporting editor plugins we will have to add those steps. Also, I think there is some of this we can automate or at least
git checkout --ours README.mdtype stuff.