From opening a bug report to creating a pull request: every contribution is appreciated and welcome. If you're planning to implement a new feature or change an existing one, please create an issue first. This way we can ensure that your precious work is not in vain.
If you have discovered a bug or have a feature suggestion, feel free to create an issue on Github.
- generate a nikita project from a local checkout of generator-nikita
- work on that generated project and commit all the changes locally
- backport the changes to the checkout of generator-nikita
- generate the project again.
- if no files are modified and test are passing your done
-
fork generator-nikita on Github
-
clone your fork
git clone [email protected]:<YOUR-USER>/generator-nikita.git
- make a new branch and set upstream
cd generator-nikita
git checkout -b myfeature
git remote add upstream [email protected]:nikita-kit/generator-nikita.git
- install npm and make sure that all tests passing
npm install
npm test
- generate a nikita project with the forked generator (yeoman needs to be installed:
npm install yo -g
)
cd ..
mkdir nikita-generated
cd nikita-generated
yo ../generator-nikita
-
answer the questions in a reasonable way for your feature or fix
-
commit the generated folder to a local git repo
git init
git add .
git commit -m"initial commit"
- make your changes (don't forget the readme), run grunt for testing and commit all
grunt
git commit -m"added my feature"
- backport your changes to generator checkout at
generator-nikita
folder
cd ../generator-nikita
- rerun the generator at the
nikita-generated
folder
cd ../nikita-generated
yo ../generator-nikita
-
answer all questions by hitting enter
-
if nothing is modified, you're nearly done
git diff
- run the tests at
generator-nikita
folder and update the changelog
cd ../generator-nikita
npm run test
- if all tests are passing, commit your changes and push them
git add <YOUR-CHANGES>
git commit -m"added my feature"
git push
After getting some feedback, push to your fork and submit a pull request. We may suggest some changes or improvements or alternatives, but for small changes your pull request should be accepted quickly.
Some things that will increase the chance that your pull request is accepted:
- update Readme and Changelog
- write tests
- follow the existing coding style
- Write a good commit message